I take a different approach: I post everything needit to the invoice in one transaction. Close transation. Number=0 in first post. If everything's ok (commit), I update the invoice number with a SP in the server, that input's RecordID from the invoice and set's invoice number.

Artur

----- Original Message -----
From: hans@...
To: IBObjects@yahoogroups.com
Sent: Friday, August 24, 2001 5:13 PM
Subject: Re: [IBO] Managing Transactions


> I think When a user opens Invoice module and selects "NEW" I have to get a transaction number and use the number in all functions transactions, then if user preses "update" for the job I must commit all the changes to database that have the same transaction number. Or selects Cancel I have to do a RollBack operation. Think that all items at detail update fires 15 Functions.
>

Just a thought.

If more than one user uses the system, you'll most likely end up
with a GAP in invoice numbers. You can build logic to minimize
those gaps and mark the last ones left with VOID. Minimizing GAP
logic with a Invoice number based on department/salesperson/invoice
number used to work well for me. Getting an invoice number only at
time of posting from a IB6 procedure run in server might work
better.

Best Regards,
Hans

Yahoo! Groups Sponsor



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



[Non-text portions of this message have been removed]