Unanswered: Splitting database application that has a form that generates automatic numbers!
I was just wandering I have an application that I need to split the db into front and backend .
I was just wandering if there would be a problem or is there anything I need to know or be aware of . I mean, I have a main form that generates automatic trans number , now if I put a copy of the frontend on different machines which would include the form and each user (only 2 users )needs to make a transaction at the same time, would there be a problem?
I would consider "reserving" your record. When the form opens, create a new record and save it immediately. Then when your user begins editting data, update the record that was just created. In this way, you will never have a key conflict with other users.
'Splitting database application that has a form that generates automatic numbers!'
Thanks for the reply to my message.
To interprete what u are saying if user A opens up the form to do a new transaction and also user b also opens up there own version on there pc to do another transaction at the same time.....u are suggesting that user A saves there form before proceeding with their transacton ....so that user B does not have access to that number when they open up their own form?