RE: Re: COM Invoice file name

["Michael Franchino" <Michael.Franchino@xxxxxxxxxx>]

The field names just roll off the tongue after 10 years of using them.
Field names are field names, when you have 1000's of fields, after a
while they start to make no sense anyway.  The S0 and S1 logicals can
really mess you up if you use the wrong ones.

Michael Franchino
Custom Systems Corporation
http://eax.cussys.com
973-726-0202 X214 



-----Original Message-----
From: Eric A. Wolf [mailto:eric_a_wolf@xxxxxxxxxxx] 
Sent: Friday, October 24, 2003 12:07 PM
To: MAPICS ERP System Discussion
Subject: Re: Re: COM Invoice file name


You cannot entirely blame Synon for the file/field naming convention.
According to a friend of mine, the field and file names are created by
Synon, but prior to creation, the developer has the option of changing
those names.  Apparently when COM was developed, they chose not to
change them.

FYI, has anyone noticed that there is no consistency with the S0 Update
Index, S1 Retrieval Index?  There was a bug in the version of Synon
during the initial development that alternated the naming of these
indexes that also could/should have been caught prior to releasing of
the product. (According to my same source).

Just a piece of useless information for the day...
Eric
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post
a message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mapics-l.