Hi John,

We are looking at the best way to provide stateless environment using cursoradapters. We have broken out the environment into 3 tiers, a presentation tier (GL_PRZ.EXE) a business tier (GL_BIZ.DLL) and a data tier GL_DAT.DLL). All of the Exe's and DLL's will reside on a NT server with each clients PC installing the Fox 8 runtimes and registering the DLL's on the server. All of our data entry forms have a toolbar attached to them for record navigation and other data functions (saving, save with new, delete etc.). We had originally set up properties in the data tier, so that when the cursoradapter opened, the cursor was created and the number of records for the cursor was set. Then when the toolbar was clicked for the next record, the data tier would move to the next record in the cursor and send back the result set to the presentation tier. That works great except, this of course is not a stateless environmemnt. With multiple users all using the same DLL's, we are assuming that these records and properties could get overriden with another PC's request for the same data.

We are assuming that this is the way it would work and does not offer protection from cursors and their properties being clobbered.

We then looked at just getting one record at a time from the presentation tier and keeping track of the last key, then passing the key to the data tier to get the next record after the key. This of course will create issues when the order that the data is presented on the form is changed.

Any ideas on the best way to use cursoradapters in a stateless environment.

Thanks in Advance

Neil.