I used one of the sample templates and modified it for our use. Still don't quite understand the vertical rules function of the specification document, but got it to work anyway.

I think my last hurdle is formating of mailing addresses. For many years I have had an internal convention that Address 3 is always the CITY and Address 4 is always the STATE (in two character abbreviations ie CA AZ NY).

I modified the billing address so that I would get the following:

Customer Name
Address_1
Address_2
Address_3 Address_4_(two characters only) Zip

This works OK but only if there is both an address 1 and address 2 in the customer record. If address 2 is blank (most of mine are), then Adagio apparently "snakes" the fields so that I get something like this:

Customer Name
Address 1
Address_3_City
Address_4_State Zip

The original sample specification had

Customer Name
Address 1
Address 2
Address 3
Address 4
Zip

Is there a work around? For those that used Accpac spec documents, my spec read as follows:

.H@7%C2
.H@7%B1
.H@7%B2
.H@7%B3 @<== %B5 @<== %B4

Thanks,
Robert

Hi Robert,

Indeed Adagio does not have a code such as @<== to move the postal/zip code immediately to the right of the city - it uses an object oriented designer rather than character based.

Perhaps if you needed this all on one line without gaps in between, then put the city, state and zip code all in the address line 4 field?

In Adagio there are 2 different sets of Address fields for printing specs (invoices, statements, etc). There are 'regular' address fields that simply print the contents of the field. There are also a second set of 'formatted' address fields - these move the zip code to print directly underneath the last non-blank address line to remove excess space. Taking the original sample spec as an example, if both Address 3 and 4 fields on the customer record were blank, the zip code would move up and print in the Address 3 slot, directly underneath Address 2 without space in between.

Thanks for clarifying this up for me . . . I'll be taking a look at my options a bit later.

Unfortunately, I do need to keep the State in A4 as it's picked up by our manifest system automatically through odbc.

Robert

Fair enough. How about an optional field on the customer record? Text optional fields hold up to 30 characters and are printable on specs. Codes C55-C57 are for Receivables Statement (and Letter) specs, and for OE documents the codes are C31-C33. All can be found in the 'Customer Info' section of the spec fields list. Using this means you don't have to change your address layout. This information can be imported from Import Customers in Receivables.

To set up optional fields, you edit the Adagio Receivables company profile and define field Titles for which optional fields you want to use. Then when editing a customer, these Titles will appear on the Credit Card tab.

Hi Robert,

Are you using the Territory field for something? Often I've seen its 2 character field used to store the "state" for reporting purposes.