× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks for the info everybody. Peter, to answer your last question - simply
put, old (and new) customers with new launches/part umbers hence new demands
(using their pnums being one of them).

Alternative ref looks the way to go for now.

Alan

-----Original Message-----
From: peterj@xxxxxxxxxxx [mailto:peterj@xxxxxxxxxxx]
Sent: Tuesday, June 03, 2003 10:34 AM
To: 'System 21 Users'; 'Alan Kincer'
Subject: RE: [SYSTEM21] Expand characters in part/item field


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.



_______________________________________________
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.


======================================================================= 
This e-mail, including any attachments, contains information from KI (USA)
Corporation which may be confidential or privileged. These contents are
intended only for the individual(s) to whom it is addressed. If you are not
the intended recipient do not copy, distribute, or take any action in
reliance on it.  

If you have received this e-mail in error notify the sender immediately via
message reply then delete or destroy all electronic and hard copies of the
communication, including attachments.  

KI (USA) Corporation's anti-virus system checks for known viruses.
Accordingly you are advised to run your own virus check before opening any
attachments received. KI (USA) Corporation will not accept any liability
once an e-mail and/or any attachment is received.  

Views expressed in the e-mail are those of the author and not necessarily
those of KI (USA) Corporation. 


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.