Lembit Soobik
Lembit.Soobik at t-online.de
Wed Jul 23 10:09:56 CDT 2003
and as for the backend, there is this great tool which some list members have put together the Backend Upgrader (BEU) which you can download free from our website Lembit Soobik ----- Original Message ----- From: "Bonnie Snider" <BSNIDER at utah.gov> To: <accessd at databaseadvisors.com> Sent: Wednesday, July 23, 2003 4:26 PM Subject: RE: [AccessD] database locked by user admin at machine ""error > Yes, I can see where that would be helpful. Thank you. > > >>> CWortz at tea.state.tx.us 7/23/2003 8:23:08 AM >>> > Bonnie, > > This is not a solution to your immediate problem, but a strategy to > follow in the future. Have two environments; the current production > environment your users are in, and a development environment for your > use. > > Both environments should start with exact copies of the production > application. You do your work in the development environment without > having to worry about any users trying to update data while you are > making your changes. When you have made all the current changes and > have thoroughly tested them, then you promote your version of the > front-end to the production environment. Usually this promotion will > only take a few minutes and can be done at the beginning or end of the > work day without disrupting the users. > > If you have to promote a new version of the back-end, then there is a > little inconvenience for either you or the users since you will have > to > make sure no users are in the production back-end while you are > copying > and converting the data to the new back-end. Depending on how big a > change you have made to the BE this could be minutes to hours, so you > may be forced to do it during non-business hours. > > I just got an e-mail from a site I frequent that they will be down for > maintenance this weekend and to expect to see some changes when they > are > back up Saturday night or Sunday morning. So they are following this > strategy. > > Charles Wortz > Software Development Division > Texas Education Agency > 1701 N. Congress Ave > Austin, TX 78701-1494 > 512-463-9493 > CWortz at tea.state.tx.us > > > > -----Original Message----- > From: Bonnie Snider [mailto:BSNIDER at utah.gov] > Sent: Wednesday 2003 Jul 23 08:55 > To: accessd at databaseadvisors.com > Subject: Re: [AccessD] database locked by user admin at machine " > "error > Importance: Low > > > 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 > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >