Crashing Database

[Mez]

Hello All,

In the last 4 days my Access database has crashed 15 times, coming up with the message 'Run Time Error 3343 - Unrecognised Database Format'. The DB is used in a multi-user environment, and has been running smoothly (ish!) for about a year, this has only just started happening. If I then get everyone logged off, and go into the DB, I get the option to repair it, which it does fine. Has anyone experianced this? Its causing me much hassle and I cant figure why its doing this.

 

[ColinEssex]

What version of Access are you using?

Col

 

[Mez]

Access 2000 ver 9.0.3821 SR-1

 

[ColinEssex]

Have a look at this thread

http://www.access-programmers.co.uk...=48712&highlight=unrecognised+database+format

 

[Mez]

Many thanks but this does not really help, the database can repair itself each time, I do not think it is actually getting corrupted, or if it is it is only minor, the fact this is happening regularly, and has only been happening for a short period of time, at first made me think it could be a virus - checked though and it isnt. Any other ideas?

 

[yeatmanj]

Did you every find a solution to this? I seem to be having similar issues. However the crashing events vary in type.

 

[RuralGuy]

Is your db split to FrontEnd and BackEnd? If not, I would highly recommend it. You might also perform the tasks described by Allen Browne here: http://allenbrowne.com/ser-47.html

 

[yeatmanj]

It is split. My issues seem to be user issues. I think it is time to build a new version off of Access 2003 and try to make it stand alone so that it will function regardless of office upgrades.

 

[Mez]

Database Crashes

Never did sort this Db is still crashing on a regular basis, I now think it is something to do with the number of concurrent users, which has grown from about 5 when I first wrote it to around 30 now. Dont think Access likes that many users, so am in the process of converting the full back end to SQL. This is, apparently, a much more robust platform, and there are loads of tools for converting that make the process pretty easy

 

[yeatmanj]

I don't know if you ran across it, but all indications point to DAO being the problem. The limitation on users should be around 255, so 30 users should not make a difference. However, with my dbs, I think that users are causing part of the problem by improperly exiting the database. Typically I can recompile and repair then all is well for a short time.

 

[Mez]

That was my first impression from the error message Access gave me, saying a user 'unexpectedly' quit the program. But I have run the Db in a test environment, with limited users, and am almost 100% certain the crash occured when all users were in the Db, and had not exited. However, I use links between Access and Word, so perhaps the error occurs when passing control between the two. Today, the Db has crashed 8 times, it is really p*****g me off, the only solution i think is too convert to SQL. Or consider a carrer change!

 

[yeatmanj]

I'm with you there. If I find anything, I will definately keep you posted.

 

[mresann]

You may have to rethink the code. First order of business: compact your front ends AND your back end on a regular basis, start with weekly, then work down to daily if the problems exist.

If you still have problems, consider creating new databases and importing all the objects from the current db to the new db. Do this for the back end first. After that, import the objects from the current db into a new db once, then copy the new front end to the stations that use the front end. (Make sure you rename the new databases with the same names as the old databases) Of course, you have to reset all your references and startup options, but this sometimes does the trick.

If you still have problems after all of that, then you will probably have to make some changes in the code, probably by getting rid of any linking processes and replacing them with DAO or ADO objects, which can be a pain, but necessary if you ever upgrade in the future.