Having gone down this same road myself, I can concur that the set lock on
"PO numbering table" and manually controling the next number, just doesn't
work. The user thought they needed sequentially numbered PO's, and if they
decided not to add a PO, then their number should still be the next PO
number. Of course if they started to add a PO, and then went for a coffee
break...

The Autonumber, even though it will skip a number if not used, is the safer
approach.

Dennis
*****



At 11:42 AM 12/16/02 -0600, you wrote:
>
>We have 8 users that access a purchase order system over a network.  The
>users are running RTime for Windows 1.851 installed on each of their
>workstations running windows 98 or windows 2000.  The database and
>programs are located on a separate computer running windows 2000.  When
>a new purchase is added to the system a number is automatically
>generated for it.  This is where the problem occurs.  We have a table
>that stores the current number and is accessed and incremented each time
>a new order is entered.  In the code, we set a lock on the table, fetch
>the current number, increment it by one, update the table, set the lock
>off and proceed to the po entry screen.
>
>For some reason, every odd couple of days and entries the number is not
>calculated properly.  I have made a log file to monitor the
>assignments.  What I see in the log file is that everything is working
>fine for all of the users and then suddenly one of the users tries to
>enter a new po.  The number that is fetched from the table is
>incorrect.  I have seen it fetch a number that was used 10 POs ago or
>maybe a number that was used 3 POs ago.  I don't understand how.
>
>I know that when RTime exits normally it erases the $$$ files and if not
>then they are left alone.  Is it possible that one of these is getting
>re-used and supplying incorrect information.
>
>Any thoughts, suggestions, ideas are greatly appreciated.
>
>Damian
>
>================================================
>TO SEE MESSAGE POSTING GUIDELINES:
>Send a plain text email to [EMAIL PROTECTED]
>In the message body, put just two words: INTRO rbase-l
>================================================
>TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
>In the message body, put just two words: UNSUBSCRIBE rbase-l
>================================================
>TO SEARCH ARCHIVES:
>http://www.mail-archive.com/rbase-l%40sonetmail.com/
>
>
Dennis Fleming
IISCO
http://www.TheBestCMMS.com
Phone: 570 775-7593
Fax:   570 775-9797
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/

Reply via email to