I wrote a stored procedure to automatically convert msaccess queries into stored procs.

Paul11/6/2001 7:27:43 PM

I wrote something that converts ALL MsAccess queries to sql stored procedures even ones that accepted parameter(s). The project I was on had over 300 various append,delete,select etc queries and I did not want to do these manually. I was able to read the select statements from the Access database and then convert them into stored proc's in the SQL database. I was even able to convert queries with parameter(s) i.e. =[Forms]![myform].[Startdate] was converted to @StartDate as Datetime in the stored procedure. This saved the me and the client at least 300 hours.

Len Komar 11/1/2001 11:33:44 PM

It is said in the subject article that Access has limited performance, scalability, multiuser capability, and database size.

From MS Access Help File I read that the maximum file size is 1GB and allows more than 200 concurrent users. These limits seem more than sufficient for most purposes. Do they apply only to a desktop rather than a Web-based situation?

Recently 5 users sitting in the same room and using 5 different computer concurrently tested a database driven site that utilizes an Access database.

There was no noticeable slowing down of the access speed.

Could anyone tell me what are the real practical constraints that developers face in the use Access database as compared to SQL in a Web-based application?

Ken
========================

Ken Chia 6/16/2000 2:30:05 AM