|
Is the field you removed to make it work numeric by any chance? The message appears to indicate an uninitialized numeric field. The "too many fields" part of the message may be indicating the field you removed occurs in a position not supported by your device, like position 81 when your device only supports eighty characters. As a side note, I experimented with SFLINZ early in my career and found it lacking. You might consider eliminating this keyword in favor of a routine that simply writes the records to the subfile as needed. If this is an inquiry type subfile, you definitely have no need for this keyword. Donald R. Fisher, III Project Manager The Roomstore Furniture Company (804) 784-7600 extension 2124 DFisher@roomstoreeast.com <clip> Message . . . . : Data sent to device VPTI2860S1 not valid. Negative response code is 10050129. Cause . . . . . : The condition was caused by the program output data containing below hex 40 or too many input fields. <clip>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
