Bonnie Snider
BSNIDER at utah.gov
Wed Jul 23 08:55:24 CDT 2003
I am the only one that does any programming edits, and I'm careful not to do it during the two weeks when we are doing the data entry. The only way anyone else gets into the database is through the data access pages. The database was created in Access 2000 (9.0.6926 SP-3). I'm not sure where to look for the system release of Jet. I found some code to let me see who was in the database so I could call and ask them if they had completed their data entry so someone else could get in, and we were able to get things done, but it was not a satisfactory solution. We will be needing to do data entry again in September, so I'd like to find a solution before then. :-) >>> martyconnelly at shaw.ca 7/22/2003 10:34:28 PM >>> It could be a lot of things. What level of Office was this developed on. What service pack and System Release of Jet, but could it be that someone is opening the mdb or adp to perform programming edits and this has to be done in exclusive mode or someone could be just opening the mdb by clicking on the file directly to do data edits. There is an option from Tools menu to force either shared or exclusive opening but this can overridden. I can give you some code to force a shared open and if some tries an exclusive open indicates machine and user name. Bonnie Snider wrote: >I have a database that resides on a netware 6 file server and serves >about 30 user across a wide area network. All users belong to a group >that has full rights to the directory in which the database is located. >Usually there will be three or four users trying to access the database >at the same time. > >Users access the data via data access pages over the internet. Some >days there are no problems with access to the database. Other days if >even one user is already logged into the database a second user will get >the error message that the database is locked by user admine at machine >"(machine name)". Sometimes they will continue to get the message >even after the first user logs out of the the database. Sometimes >they are able to open the access pages, but then are unable to enter >data. Any suggestions or ideas as to what the problem may be? > >Bonnie Snider, LAN Administrator >DWS North Admin >Phone: 526-9253 >Cell: 430-1219 >FAX: 526-9744 >EMAIL: bsnider at utah.gov > > > _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com Bonnie Snider, LAN Administrator DWS North Admin Phone: 526-9253 Cell: 430-1219 FAX: 526-9744 EMAIL: bsnider at utah.gov