Shamil Salakhetdinov
shamil at users.mns.ru
Thu Feb 14 18:02:05 CST 2008
Hi Jim, Yes, MS SQL is a good modern alternative but if you use MS Access and if there is no that much workload on Web Server MS Access mdb could be good enough... ...AFAIK ASP.NET 2.0 runtime by default has just 12 worker threads for one web app, and it's an easy task to serialize code execution of critical code paths... ...I personally do use MS SQL with Web apps but for small/not heavy loaded web apps MS Access backend should work well I'd expect... -- Shamil -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Thursday, February 14, 2008 11:49 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] MDB on the web Hi Shamil: I will try and convince the client to go MS SQL... speed, reliability and features. Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil Salakhetdinov Sent: Thursday, February 14, 2008 9:51 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] MDB on the web Hi Jim, If: - your (client's) mdb is local to the web app and - you develop ASP.NET 2.0 web apps Then you can use relative references to MS Access mdb within .aspx web pages like that: <asp:AccessDataSource DataFile="~\App_Data\nw.mdb" ... -- Shamil