When setting up an Access datasource on CF, you should ALWAYS uncheck the "Maintain Database Connections" box under CF Settings > in the ODBC Data Sources administrator. CF hangs on to the connection and can lock out other users trying to access the same tables. Access is not a very good RDBMS for web applications. 2000 is much better than 97, but still is not real good.
Dave ----- Original Message ----- From: "LANCASTER, STEVEN M. (JSC-OL) (BAR)" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Monday, March 18, 2002 7:07 AM Subject: RE: Database locked by admin? While using Access you may want to set you session variables for a shorter period of time, so that when CF accesses the database it will also let go in a short amount of time. Steven Lancaster Barrios Technology NASA/JSC 281-244-2444 (voice) [EMAIL PROTECTED] -----Original Message----- From: Dave Carabetta [mailto:[EMAIL PROTECTED]] Sent: Sunday, March 17, 2002 2:57 PM To: CF-Talk Subject: Re: Database locked by admin? > I am getting an error message about my database being locked by 'admin' and > was wondering if anyone out there has any suggestions: > > > Message: ODBC Error Code = S1000 (General error)<P> > Native error code: -1102 > SQLState: S1000 > Detail: [Microsoft][ODBC Microsoft Access Driver] Could not update; > currently locked by user 'admin' on machine 'MYMACHINE'.<P><P>Data Source = > "mydatasource"<P> > > > In the archives I found that this may be because the database is corrupt -- > I've run the compression/correction option on it (MS-Access database), but > this keeps happening. > > The database this error occurs on is my visitors log -- for every page hit I > write out a record w/ the HTTP referrer, USER_AGENT, date/time, etc. The > website isn't high-volume at all (i.e. averaging around 1000 page hits/day), > but when these errors come up IS when there are a relatively large number of > page requests (for this website) within a short period of time. ODBC > problem? MDAC? Need to upgrade to SQL server? :) > First off, I would highly recommend against using Access in a production environment. While 1000 hits/day isn't exactly Amazon.com volume, that's a respectable number and you should consider looking into an upgrade to a RDBMS such as SQL Server. The problem with access is that only one person may access (no pun intended) the DB at a time because an Access database is by default set up to be opened exclusively. So if two people concurrently try and hit the database, Access will lock the other user out -- hence your error. I doubt it's a corruption thing, although I don't know what your DB looks like either. Make sure nobody has the database open in the Access program itself. This also causes an exclusive lock that will prevent others from accessing it. But, again, if you're at 1000 hits/day and that number may go up, I would highly recommend looking into a more suitable solution such as SQL Server, MySQL, Oracle, etc. Regards, Dave. ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
