Okay, found the answer to this the hard way - opened a Microsoft incident. Turns out it's a bug they don't intend to fix. Same thing happens in Access .dap (data access pages, the webified version) - all the recordset caches locally and user A can't see user B's updates until they manually refresh the recordset. How do you manually refresh? Either close/open the form or reload the browser; or put a button on it that forces a refresh. <sigh>
I'll be building a hand-coded web version here shortly. What good are MS tools if they don't work right? Or at least have selectable options to work right. :-) Tim ---------------- [Myself, previously] We're trying to update a SQL server backend using Access 2002 .adp forms as a frontend. It's working as far as updates go, but the problem we're having is that the .adp form apparently caches the recordset locally and so concurrent users don't see each other's updates. We're working with a recordset of about 7000 entries, all of which pull down local when the form is opened. It's detecting when one user updates a record and then another user tries to update the same record (message box of Save/Cancel/Copy to Clipboard), but ideally what would happen is that only the record being edited would be cached on the local form and released when saved so that other users can immediately see the updates if they go to that record. Setting the MaxRecords to 1 just pulls in one record and won't allow navigation to any others. :-) ___________________________ Tim Furry Web Developer Foulston Siefkin LLP ____ � The WDVL Discussion List from WDVL.COM � ____ To Join wdvltalk, Send An Email To: mailto:[EMAIL PROTECTED] Send Your Posts To: [EMAIL PROTECTED] To change subscription settings to the wdvltalk digest version: http://wdvl.internet.com/WDVL/Forum/#sub ________________ http://www.wdvl.com _______________________ You are currently subscribed to wdvltalk as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED]
