In building a website, is there any formula for determining when to use 

Access or when to move up to a larger program such as SQL or Oracle?



Thanks in advance for your help



Charles E. Brown

Money.  Hardware.  Size of the site.  Time to market.  Database expertise.

There are a lot of things to consider.



-----Original Message-----

From: chabrown@b... [mailto:chabrown@b...]

Sent: Thursday, July 19, 2001 3:28 PM

To: Access

Subject: [access] Access vs. Larger Databases





In building a website, is there any formula for determining when to use

Access or when to move up to a larger program such as SQL or Oracle?



Thanks in advance for your help



Charles E. Brown

I've heard it said that Access works well as a database if you've got under

5 users, or under 20mb of data in the table you're using.



I've had many problems with clients who insisted on using Access with 20

users, or more than 60 mb...  The problem is that Access won't queue

requests in the same way that SQL Server (the mid-range solution) or better

dbms products can.  Instead of queueing, you just lose data, which is quite

frustrating.



If you can, go with at least SQL Server, which at least meets the

entry-level ANSI SQL specifications (Access does not).  I feel comfortable

with Access when there are very few users, or the database is very small...



-----Original Message-----

From: chabrown@b... [mailto:chabrown@b...]

Sent: Thursday, July 19, 2001 3:28 PM

To: Access

Subject: [access] Access vs. Larger Databases





In building a website, is there any formula for determining when to use

Access or when to move up to a larger program such as SQL or Oracle?



Thanks in advance for your help



Charles E. Brown