Unable to compactrepair database

Well Duane, there's no nice way to put this. You're wrong! A well designed Access-JET database will do almost anything, at at least 1-3 the cost of SQL-Server, that a company needs to do as long as the scale is within Access's specifications.

I've been writing databases since 1981, Access databases since 1992, and as a professional developer for more than 10 years, and have yet to find a system as versatile as Access.

The applications I currently support have 53 users on 15 front-end databases and 1 asp front-end all against a single 100 MB JET back-end. It is quick, despite users having as many as 3 front-ends open, and probably as many as 65 concurrent connections. At any given time, there can be 8 asp users, 5 users on Terminal Server, and 40 users on the LAN. We haven't had a corruption since April of 2003 when a bad WiFi card repeadedly dropped connections. Not only that, a truncated copy of the database has been running on a web server getting an average of 5,000 hits a day (maybe 3,500 pageviews) with only a single problem since 2001. The same web server runs a SQL-Server database which was down for a day when the Sbutter worm hit. In all the years I've been running Access, I've lost under 2 dozen records from corruption, and most of that corruption was due to user error (turning off a machine during a write).

SQL-Server is a fine database engine too. I use it when I need better security (hospital records, etc.), when I have a lot of users, (75 or more), when I have large databases (over 500 MB), or when a client with money to burn insists on it. -- Arvin Meyer, MCP, MVP Microsoft Access Free Access downloads