...
5) change the column width in AVS but do not change the forms and reports
This is not viable. For details read on. Expanding AVS's STREET_NUMBER_SFX field to 10 characters has expected results: in some cases Oracle Forms truncates it to 1 character ("H" or "1", for "HALF" or "1/2"), in some cases, the form just fails to handle/process the address correctly, in some cases the form displays a popup that a text field is not wide enough. As mentioned before, each of the 100s of form/reports/web applications that uses addresses would need to be modified to handle the expanded field.
6) add a new char 10 column to AVS to hold the full number suffix
(this is a naive attempt since I do not know DBI business)
Add trigger code to keep the existing number suffix column in sync with the new number suffix column.
When there is an insert or update on new number suffix column
if there is one char, copy it into the existing number suffix column.
if there is more than one char, copy a special char into the existing number suffix column.
When there is an insert or update on existing number suffix column take the character and put it into the new number suffix column.
For this to work there must be a way for the user to disambiguate apparently identical columns.
...
longitude
EAS Field: address_base.geometry.longitude (double)
XML Field: base_address/longitude
FGDC Field: address longitude (double)
AVS Field:
Example:
Comment:
...