|
Do you need to use 30 characters INTERNALLY or just eg to print on some customer documentation? If the latter I'd suggest you use the alternate reference field (which does accommodate 30), keep a <15 internal part number, and modify only the output programs. I was involved once with a customer who required more than 15 everywhere, the recompilation of the database was the simpler part - accommodating 30 on each screen on print was the big effort, but as I recall we managed to compromise by limiting the item description to 20 characters, so where the code and description are displayed together (probably most occurrences) the total space remained about the same. Also 10's of thousands of parts only had only a few hundred different descriptions (many were simply eg "filter"), so these could be encoded and recovered from a new table - this also simplified multi-lingual descriptions. Surely if this had been an initial requirement, you should not have implemented System 21, so why has this suddenly become an issue? Peter Joel Saltway Ltd -----Original Message----- From: system21-bounces@xxxxxxxxxxxx [mailto:system21-bounces@xxxxxxxxxxxx] On Behalf Of Alan Kincer Sent: 02 June 2003 17:18 To: jbausers-l@xxxxxxxxxxxx Subject: [SYSTEM21] Expand characters in part/item field Currently we are limited to 15 characters in the part field. We have a need to expand this to 30 characters. Can anyone tell me the issues and pitfalls associated with this? Thank you! Alan _______________________________________________ This is the System 21 Users (SYSTEM21) mailing list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/system21 or email: SYSTEM21-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/system21.
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.