I think the article you mention gives the answer to 'what's the view in the cf community':
"The Access ODBC Driver and Microsoft OLE DB Provider for Microsoft Jet are not intended to be used with high-stress, high-concurrency, 24x7 server applications, such as web, commerce, transactional, messaging servers, and so on." Why use Access at all? If a commercial DBMS isn't a viable solution, why not use MySQL or Postgre or Interbase (or it's open source cousin, Firebird). My .02 -------- >Date: Tue, 29 Jan 2002 15:22:28 +1030 >From: "Parker, Kevin" <[EMAIL PROTECTED]> >Subject: JET >Message-ID: > ><[EMAIL PROTECTED]>.au> >This was drawn to my attention today (extract below) and I >traditionally >use >Access via an ODBC connection for small apps. The full article can be > >found >at http://support.microsoft.com/default.aspx?scid=kb;EN-US;q222135 >******* >When running Microsoft Jet in an IIS environment, it is recommended >that >you use the native Jet OLE DB Provider in place of the Microsoft >Access >ODBC driver. The Microsoft Access ODBC driver (Jet ODBC driver) >can have >stability issues due to the version of Visual Basic for >Applications that >is invoked because the version is not thread safe. As a result, when >multiple concurrent users make requests of a Microsoft Access database, >unpredictable results may occur. The native Jet OLE DB Provider includes >fixes and enhancements for stability, performance, and thread pooling >(including calling a thread-safe version of Visual >Basic for >Applications). ******** >What's the view in the CF Community - should I switch strategies here -> is >this a problem using CF? _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
