 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Multiuser / Networking / November 2007record-level locking fix in KB238258 does not work
Hi, I have an Access 2002 database (split into front-end and back-end) with a workgroup for users to login from. I set up all the forms and Options to use record-level locking, but when you edit one record, you'll lock several of the surrounding records (i.e. page-locking). My searches led me to the knowledge base article 238258, but I cannot install the Office 2000 SR-1/SR-1a fix because we have SP3 for Office 2000 installed. I have confirmed that if I do not use the workgroup to log into the database Access uses record-level locking. Has anyone else come across this or have any suggestions ? Thanks, Tim K. You are confusing me here, that article 238258 applies to access 2000 Are you using access 2000 here? Also, that article notes that when you don't use a shortcut, the record level locking works. So, can I assume that when you don't use a shortcut, your record level locking works?  SignatureAlbert D. Kallal (Access MVP) Edmonton, Alberta Canada pleaseNOOSpamKallal@msn.com Hi, Yes, the KB article says it applies to Access 2000. And I am using Access 2002, but I am having exactly the same issue reported. You are correct, if I do not use the shortcut to open the database, record locking works as you would expect. Unfortunately, I must continue to use the shortcut so the workgroup file can log users in. Any ideas ? Thanks ! -Tim > You are confusing me here, that article 238258 applies to access 2000 > [quoted text clipped - 5 lines] > So, can I assume that when you don't use a shortcut, your record level > locking works? > if I > do not use the shortcut to open the database, record locking works as you > would expect. Unfortunately, I must continue to use the shortcut so the > workgroup file can log users in. > > Any ideas ? Perhaps you are still using a2000 format? (but, to be honest, I would have "guessed" that your problem would not occur in a2002 and later).... I assume you gone: tools->options->advanced Make sure the following option is checked: [x] check the Open databases using record level locking. Here is two more things to try: (I don't have a2002 with me). You could "set" the row locking in your startup code: eg: Application.SetOption "ShowWindowsInTaskbar", False Application.SetOption "ShowWindowsInTaskbar", False Application.SetOption "Themed Form Controls", True Application.SetOption "Show Startup Dialog Box", False Application.CommandBars.AdaptiveMenus = False application.SetOption "Use Row Level Locking",true Note the above last setting.... So, try converting your application to a2002 format (the default is 2000 format). And....If that don't work, then try the above in your startup code..... SignatureAlbert D. Kallal (Access MVP) Edmonton, Alberta Canada pleaseNOOSpamKallal@msn.com Thanks for your suggestions. I converted the backend databases to 2002 (the front end was already 2002) and as you suspected, that did not have any effect. I also tried out the SetOption suggestion and that did not appear to have any effect either. The "Open databases using record level locking" was also checked. I'm not certain if you have any other ideas, but I was thinking of setting up a test database (one without sensitive material but similar in structure/setup) in case I need to put a call in to Microsoft Tech Support. I don't know if the news group allows attachments, but I could send that db to you as well. Thanks again, Tim K. > > if I > > do not use the shortcut to open the database, record locking works as you [quoted text clipped - 35 lines] > > And....If that don't work, then try the above in your startup code..... You have checked the obvious settings on the forms..right? Regardless of the "row locking", each form still have to be set to lock the record, or the table. Perhaps you have a form set to lock a whole table...... I not seen your problem posted here, and it certainly not a regular problem. So, those settings don't change the forms as to if the current record is locked. (the setting DOES change how a form locks records IF THE FORM IS SET to lock records). However, since you mentioned things DO work without using a shortcut, then the above would not apply to you. I would perhaps try joining the workgroup file, and then launching not using a shortcut...and see if that works. Like I say, that problem refers to a2000, and you not using that version.... SignatureAlbert D. Kallal (Access MVP) Edmonton, Alberta Canada pleaseNOOSpamKallal@msn.com ÇÔÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ > You have checked the obvious settings on the forms..right? > [quoted text clipped - 18 lines] > using a shortcut...and see if that works. Like I say, that problem refers > to a2000, and you not using that version.... Yes, you have proved you can post to this newsgroup. No, you have not contributed either questions or answers about the subject, which is: using Microsoft Access database software in a multiuser environment. If you are looking for conversation, find a chat room; if you are trying to prove you are a juvenile or have a juvenile attitude, you have accomplished that; if you are looking for "pen pals," look for a newsgroup in USENET. Larry Linson Microsoft Access MVP > ÇÔÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ >> You have checked the obvious settings on the forms..right? [quoted text clipped - 19 lines] >> using a shortcut...and see if that works. Like I say, that problem refers >> to a2000, and you not using that version.... |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.