Corrupt Database

Hello all,

My issue is this, I have an application that I am developing/supporting for my company that stores it's data in a Jet (MS Access) database. This proves to be unfortunate, as the database becomes corrupted (quite often) causing the application to become useless until I manually repair the database. I guess what I'm trying to figure out is: Is this "unstability" something that other developers encounter on a regular basis, or is it something I am doing wrong in the development of the database and/or the application code....maybe both? Perhaps MS Access cannot handle the large amounts of data. I would appreciate any suggestions, tips, or pointers.

Pulling my hair out & thanking you in advance,
Rippin

[Gary Grant]

One question (well three). What version of Access, how many concurrent users (if more than ten you may want to consider SQL server) and what type of networking (M$, Novell, Banyon, etc.)?

[ufo]

You can develop auto-repair system. We had this problem and developed AutoRepair function which was used when first open failed then we tried to ato-repair and then if fail we would stop app.

There are many way how to develop this function very easy is DAO, JRO and so on.


[ufo]