What's my best option??

Currently, we are using Access as our main database
application. There are approximately 30 individuals whom
may access the database at the same point in time. My
concern is that Access may not be equipped enough for the
information that we are entering. Unfortunately, we have
been experiencing discrepancies with the information
presented on the reports.

Would you suggest Access as our main database? If so,
what could we do to prevent the corruption of the
database again in the future? If not, what would be our
other option?

"Discrepancies with the information presented in reports" does not sound
like database corruption to me.
Database corruption is usually evident in #### entries instead of expected
data, in not being able to open the database, or in unexpected or
seemingly inappropriate error messages.

Your problem more likely lies either in the design/coding of the database
itself, or in inappropriate use by your users. Neither of these problems is
going to be addressed by moving to any other database system.

30 users is a number which can be supported comfortably by a well-designed
Access database, but which can cause problems in a poorly-designed one. If
you don't know much about the difference, and especially if you expect the
number of users to grow, you might be well advised to seek some professional
assistance.

HTH
- Turtle

"Lisa" wrote in message
...
Currently, we are using Access as our main database
application. There are approximately 30 individuals whom
may access the database at the same point in time. My
concern is that Access may not be equipped enough for the
information that we are entering. Unfortunately, we have
been experiencing discrepancies with the information
presented on the reports.

Would you suggest Access as our main database? If so,
what could we do to prevent the corruption of the
database again in the future? If not, what would be our
other option?

Access can hold a lot of information...over 2gigs i think. If your DB
is really too big for that than you may want to convert it to SQL. I'm
not sure how to do that. I have however heard of Access DBs where
tables have over 50,000,000 records. There are size limits to Access
though and it may not be suited for larger companies. I think it may
be worth your time to look into SQL conversion.


------------------------------------------------
~~ Message posted from http://www.ExcelTip.com/
~~View and post usenet messages directly from http://www.ExcelForum.com/

Lisa,
30 users is not too many for a well designed Access database. Your problem
may lie with the design of the database or the design of the reports being
used to present the data. Do you have one person or group of persons
designing reports according to a company standard? Or does each user have
the capability of creating their own reports?

If you decide to use something other than Access, you will probably want to
move to a client/server database like SQL Server or Oracle.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm


"Lisa" wrote in message
...
Currently, we are using Access as our main database
application. There are approximately 30 individuals whom
may access the database at the same point in time. My
concern is that Access may not be equipped enough for the
information that we are entering. Unfortunately, we have
been experiencing discrepancies with the information
presented on the reports.

Would you suggest Access as our main database? If so,
what could we do to prevent the corruption of the
database again in the future? If not, what would be our
other option?