ACAS is used in platforms for : Linux, Unix (various), OSX, Windows
from the very old to v10, mainframes and minis (mid-frames) even down a
a few cases to the Raspberry Pi 3 with external usb hard drive/s.
ACAS used in many countries and while on sites using *nix I can use
the environment variable LC_ADDRESS to work out the format of addresses
under Windows I cannot, coming to think about that OSX may also not
handle these.
Excluding (2) then I have to cater for zipcodes, postcodes, counties
(in the UK), prefectures in France, which can give short or long
addressing so ACAS cannot used fixed address fields which is why a
variable method is used with a address delimiter and the bar "|" is now
the default at least on v3.02 as others can conflict with rdb system
such as slash, percent etc. So far no one has reported issues with the
bar but you can change that if your addressing actual uses it sometimes.
So far I have not had reports of 96 chars being too short - well at
least over the last 50 years.
Oh, one Cobol vendor has converted to their product that generates Java
but that is still under development as far as I know and that compiler
is available FOC for the Pi and no I have not bought one at least yet
but worth considering as with Java the screen handling can be brought
into the 21st century making full usage of GUI screens but I have not
seen the o/p from it so I am awaiting.
The use of the delimiter is normally only used inside the data files
although there is a dump program for sales and purchase that provides
the address as entered but that is for validation of data more than as a
normal report.
Vince
On 16/06/17 14:04, John Grillot wrote:
I'm curious about why you chose to use the address details delimiter
character approach as opposed to having separate fields for city & state?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm curious about why you chose to use the address details delimiter
character approach as opposed to having separate fields for city & state?
Thanks,
John
Reason is simple-ish:
ACAS is used in platforms for : Linux, Unix (various), OSX, Windows
from the very old to v10, mainframes and minis (mid-frames) even down a
a few cases to the Raspberry Pi 3 with external usb hard drive/s.
ACAS used in many countries and while on sites using *nix I can use
the environment variable LC_ADDRESS to work out the format of addresses
under Windows I cannot, coming to think about that OSX may also not
handle these.
Excluding (2) then I have to cater for zipcodes, postcodes, counties
(in the UK), prefectures in France, which can give short or long
addressing so ACAS cannot used fixed address fields which is why a
variable method is used with a address delimiter and the bar "|" is now
the default at least on v3.02 as others can conflict with rdb system
such as slash, percent etc. So far no one has reported issues with the
bar but you can change that if your addressing actual uses it sometimes.
So far I have not had reports of 96 chars being too short - well at
least over the last 50 years.
Oh, one Cobol vendor has converted to their product that generates Java
but that is still under development as far as I know and that compiler
is available FOC for the Pi and no I have not bought one at least yet
but worth considering as with Java the screen handling can be brought
into the 21st century making full usage of GUI screens but I have not
seen the o/p from it so I am awaiting.
The use of the delimiter is normally only used inside the data files
although there is a dump program for sales and purchase that provides
the address as entered but that is for validation of data more than as a
normal report.
Vince
On 16/06/17 14:04, John Grillot wrote:
This makes a lot of sense about the delimiter. Thanks.
Did forget one other point but is self implied -
Many businesses deal with customers and suppliers out side their country
so the address formats can be very different.
Vince
On 17/06/17 04:29, John Grillot wrote: