On Wed, Feb 3, 2010 at 2:29 PM, MB Software Solutions, LLC <[email protected]> wrote: > Sytze de Boer wrote: >> I have had identical problems to what you describe. >> My scenario was a little different where there were some 15-20 users >> creating invoices and/or purchase orders and/or general ledger >> entries. >> All required a unique id number >> >> I overcame the problem by using a table with an AUTOINC field >> I haven't encountered this problem since. > > > AUTOINC is the perfect solution, imo, unless you're not using INTEGER > keys. (But I still think they're the easiest.) -------------------------
Isn't it a bad idea to use a key's value? A key is nothing more then a pointer to a row. -- Stephen Russell Sr. Production Systems Programmer CIMSgts 901.246-0159 cell _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
