Travis wrote:
> Our accounting package's "documented interface" with it's built-in
integrity checks- likes to unpredictably (yet frequently) steal lines from
imported
EDI POs and place them on manually entered POs our sales people may be
entering.<
Sounds like the underlying DB was designed poorly. I almost always make the
PO number the primary key. Or, if importing a PO with SDQ segments (by store) a
concoctinated key of PO + Line Item. The system simply won't let it in. You
could even trap the duplicate error and display a nag screen. "PO already
entered" or something.
---------------------------------
Do you Yahoo!?
Get on board. You're invited to try the new Yahoo! Mail.
[Non-text portions of this message have been removed]
...
Please use the following Message Identifiers as your subject prefix: <SALES>,
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Job postings are welcome, but for job postings or requests for work: <JOBS> IS
REQUIRED in the subject line as a prefix.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/EDI-L/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
