Why don't you work around it by using the foreign language
functionality? Just pick some obscure languages, place a different
description in it and change that customer to use that language
Or
Add a customized fields, then add that to your forms instead
Gary Parfrey
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of bchguessing
Sent: 28 November 2006 04:40
To: vantage@yahoogroups.com
Subject: [Vantage] Multiple Part Descriptions (Version 8.00.810)
As a small OEM manufacturer we do our best to limit how much of our
supplier information gets to our customers to avoid them going
direct. Our problem to solve is to deliver multiple part descriptions
throughout the software. Anything that goes to our customers (sales
orders, quotes, invoices, etc...) we would like a generic part
description. Internally we would like a more detailed part
description. Two possible solutions would be to either use the
foreign language description or spare character user field. Does
anyone have any better solutions?
[Non-text portions of this message have been removed]
functionality? Just pick some obscure languages, place a different
description in it and change that customer to use that language
Or
Add a customized fields, then add that to your forms instead
Gary Parfrey
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of bchguessing
Sent: 28 November 2006 04:40
To: vantage@yahoogroups.com
Subject: [Vantage] Multiple Part Descriptions (Version 8.00.810)
As a small OEM manufacturer we do our best to limit how much of our
supplier information gets to our customers to avoid them going
direct. Our problem to solve is to deliver multiple part descriptions
throughout the software. Anything that goes to our customers (sales
orders, quotes, invoices, etc...) we would like a generic part
description. Internally we would like a more detailed part
description. Two possible solutions would be to either use the
foreign language description or spare character user field. Does
anyone have any better solutions?
[Non-text portions of this message have been removed]