I guess it was introduced/used for the POS when sometimes you don't know anything about the customer. Note that since October there
is now the possibility to associate a customer (party) with a sales (order). And you can even create users from the POS and
associate promo to them. But obviously _NA_ it still needed. Now that I think about it, it was maybe even there before (the POS was
introduced in fall 2004) because of anonymous customers in eCommerce...
Jacques
From: "BJ Freeman" <[email protected]>
_NA_ is to satisfy the DB FK.
many times all the records that satisfy a FK or Index are not put in.
so the record will not show on find.
the _NA_ record satisfies that requirement.
Apparently someone decided to use it as a partyID which is not goood design.
since I don't have the original message I can't go further.
=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation
<http://www.businessesnetwork.com/automation/viewforum.php?f=93>
Specialtymarket.com <http://www.specialtymarket.com/>
Systems Integrator-- Glad to Assist
Chat Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>
chris snow sent the following on 4/14/2010 11:47 AM:
Hi BJ,
I don't fully understand your response, can you please elaborate?
Many thanks,
Chris
