|
Dear Jim, Congrats on finding the problem with that GCR file query! Now, unless there was substantial tinkering with the query definition, then the output file library assignment wasn't the only problem with the extract. Why? Because GCR has many fields with mangled column headings ... and ... bad field edit codes cause dates to appear as large numbers with commas. Decipher (tm) software permanently improves BPCS data clarity for approximately 30,000 fields. http://www.unbeatenpathintl.com/decipher/source/1.html Decipher is one of our Bells & Whistles® for BPCS products: http://www.unbeatenpathintl.com/bells/source/1.html Here are two 'before-Decipher' / 'after-Decipher' illustrations based on the GCR file: >Field name: CREDAT before Decipher: query column heading ---> Date 8,0 value presented ---> 99,991,231 after Decipher: query column heading ---> Effectiv Date value presented ---> 9999/12/31 >Field name: CRDESC before Decipher: query column heading ---> Filler 100 value presented ---> Loan Payable after Decipher: query column heading ---> Account Description value presented ---> Loan Payble These problems exist for BPCS versions 6.x and higher. The origin of the column heading problem is AS/SET --- when AS/SET generates objects it mangles column headings. The orgin of the bad edit codes/edit words is simply this: imprecise programming. Warm regards and peace to you, Bob Kohlndorfer Unbeaten Path International toll free North America: (888) 874-8008 International voice: (262) 681-3151 upi@xxxxxxxxxx www.unbeatenpathintl.com +++++++++++++++++++++++++++++++++++++++++++++ From: jreinardy@xxxxxxxxxxxxxxx To: bpcs-l@xxxxxxxxxxxx Sent: Wednesday, March 24, 2004 9:06 AM Subject: RE: Missing CEA Accounts Thanks to those who responded to this. We did find the issue late Monday. A user had run a query to create a partial extract of the GCR file. Unfortunately, the output file was also called GCR and she placed it in a library that was earlier in her library list than the production files. Therefore, CEA was using a bad GCR file and giving us strange results. Renaming the file cleared up the issue. We are now reexamining security on our libraries! Regards, Jim Reinardy
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.