If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Record Locking with SQL 2000 back end
Rather than have users be able to directly open the back end tables I have
forms with Datasheet views that allow the users to open the raw data in the tables. Each form has one of the tables as its record source and has all the fields on the form locked and the table has No additions, deletions, edits, etc. I have a problem with some of the larger tables where a user will open up the datasheet form and keep it open. This ends up preventing other users from editing data even though this person with the datasheet form is just sitting on say record 150 while someone is trying to edit record 5000. Once the datasheet form is closed, editing can proceed normally. What can I do to allow users to see the full table of data, but stop this from locking out other users. SQL 2000 SP3 back end using Access 2003. |
#2
|
|||
|
|||
Jordan wrote:
Rather than have users be able to directly open the back end tables I have forms with Datasheet views that allow the users to open the raw data in the tables. Each form has one of the tables as its record source and has all the fields on the form locked and the table has No additions, deletions, edits, etc. I have a problem with some of the larger tables where a user will open up the datasheet form and keep it open. This ends up preventing other users from editing data even though this person with the datasheet form is just sitting on say record 150 while someone is trying to edit record 5000. Once the datasheet form is closed, editing can proceed normally. What can I do to allow users to see the full table of data, but stop this from locking out other users. SQL 2000 SP3 back end using Access 2003. I have definitely seen this behavior when opening table links directly, but I was under the impression that forms wouldn't have this problem. Perhaps a datasheet form is too similar to opening the table directly. ListBoxes and ComboBoxes can do this as well until the last row is accessed so doing a GoToLast might solve your problem too. That might also cause a lot of data to be dragged over the network though. Basically it is just a bad idea to open forms with large recordsets in a Client Server environment. There should always be a WHERE clause limiting the recordset to the bare minimum (one record being the best). -- I don't check the Email account attached to this message. Send instead to... RBrandt at Hunter dot com |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
ADP 2000 deployment problems | [email protected] | General Discussion | 25 | June 16th, 2005 04:52 AM |
Need Help In Printing Current Record in Specific Report | RNUSZ@OKDPS | Setting Up & Running Reports | 1 | May 16th, 2005 09:06 PM |
Code Not Working | DS | New Users | 11 | May 9th, 2005 10:55 PM |
strategy for data entry in multiple tables | LAF | Using Forms | 18 | April 25th, 2005 04:04 AM |
Executing SQL Server 2000 Stored Procs | Thom Anderson | General Discussion | 0 | April 13th, 2005 11:44 AM |