Chris,
To answer your question:
>It might help if you told us *why* you want to do this?We have an application involving wireless devices that synchronizes with a backend application. The synchronization process starts by application on the wireless device asking for a block of id numbers from the backend application. The application on the wireless device then writes the id numbers into the records on the device. Next the wireless device sends the records to the backend with the id numbers. This makes the synchronization proces idempotent so if a failure occurs in the middle of the synchronization it can just be started over. Since the id numbers are in the records the backend can detect duplicates.
Needless to say for a test, a request needs to be made for the id number(s) before the request to synchronize a record is made.
I can get around it by resetting the backend database to a known state but that is problematic.
thanks, Chris Marshall
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
