repair the database DESPERATE

[chirpyform]

I had a database in Access 97 and I converted the database to be in version 2000. This was 3 months ago. Since then I have been happily using the database in its new form on Windows NT. This week we have changed from NT to Windows 2000. Now we have the error message "Someone has closed the database incorrectly and now the database must be repaired"!!!!
We have 3 months of project work in the database and losing this information is unthinkable but at the same time we cannot continue to repair the database every 30 mins.

DESPERATELY IN NEED OF A SOLUTION AND FAST!!!!
Any help please

Chris

 

[kevinf2349]

Have you actually tried dunning the repair utility yet? If not I would give that a try.

As for losing the work....are you not taking backups?

 

[KenReay]

Hi

Are you saying you have this mesage continually?

I have clients using Access2K on Win2k with no problem

This problem is normally caused by a PC 'crashing' while updating the database, or a user existing from the database and/or windows without closing down eg power off

How many users do you have?

is the network reliable or are you having system crashes

how often is it happening



Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK

 

[chirpyform]

We repair the database every 30 mins which does in fact entail the repair utility. So yes we have tried the repair utility.

We are never more than 4 to use the database at once. It is not a problem of a crash of the computer or other reasons along these lines as the problem arrises suddenly while we are using the database. It is working fine for half an hour perhaps (sometimes less) and then suddenly there will be a message saying that the database is perhaps not in fact a database. We can continue to work on the database with this message coming up every now and then. If we quit the database and then reopen it we get the message demanding us to repair the database.

Many thanks for your help and time

Chris

 

[KenReay]

Hi

Do you have the Application split into front end / back end, with the front end located on the users C: drive and the back end located on a network share?

Is the network performance poor ie are you perhaps getting time outs when communicting with linked tables?

Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK

 

[SiJP]

Couple of solutions to try...

1) Create a new Acces db and import all the old data into it.

2) Run the JetComp tool from microsoft.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;273956

(or type JetComp into google)

3) Switch your PC back to NT.

Let me know how it goes....

 

[pweegar]

Take at look at the following: Microsoft Knowledge Base Article - 300216.

I did a google search for repair access 2000 db. Seems to be a lot of info out there.

 

[chirpyform]

Thanks for the information.

I tried importing all the objects from the database into a new database and then I had problems with the compiltor that was telling me that :

Dim db as database

was an error. Anyway thanks for all your help. If I find a solution I will let you know. It seems to me that it is a problem with the network and now the database is corrupt.

The database is entirely on the network there is no sense of front end or back end.

Thanks again

Chris

 

[chirpyform]

I took an old version of the database and imported the new data. Also it seems that the file idb was corrupt. Another user was in the file 2 times. The user killed the process rebooted the computer and now we don't seem to have the problem...

We'll see

Thanks for all your help

Chris

 

[KenReay]

Hi

You did not answer my question directly about split database, but it is clear from your last post (importing data) that it is not split. This will give you problems accepted wisdom is to split the database into frontend/backend

the reason for your error on Dom Db as Database is that Access 2000 defaults to ADO, instead of DAO, you need to add a reference to DAO using tools \ references, also it is wise to qualify data objects so Dim Db as DAO.Database, becuase some object names are common to DAO and ADO

Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK