> > > I have written an application that was upgraded from V97 to 2000 and 

> > after 

> > > some time a crash occurred causing an error message (the longest in 

> > > existence????) to appear stating "The database is in an unexpected 

> > > state..." and suggesting that the cause was that a DAO 

CompactDatabase 

> > > method had been used (it hadn't) and suggesting that the Convert 

> > Database . . . . etc. 

_______________________________

Dear David



Does this sound familiar . . .



I have written an application that was upgraded from V97 to 2000 and after 

some time a crash occurred causing an error message (the longest in 

existence????) to appear stating "The database is in an unexpected 

state..." and suggesting that the cause was that a DAO CompactDatabase 

method had been used (it hadn't) and suggesting that the Convert Database 

option on the Tools menu be used (you can't as you can't open it or import 

it). It also suggests recreating the database and just importing the 

tables and queries. 

I created a new database from scratch, using Access 2000, with new forms 

and imported the tables, queries, reports and macros from an earlier 

backup. I have used no modules and hardly any code as I have used the 

macros instead.

This has worked fine for a few weeks and now it has happened again!  At 

the time a report was being print/previewed.



I can find no mention of this particular error on the MS Knowledgebase. 

Have you any information please? 



It is running on a small NT BackOffice system with NT workstations.



____________________



I have posted this on this site and had no responses. I have sent the 

question to Woody Access Watch twice with not even an acknowlegement. I 

have made a chargeable support call to ICL (Microsoft support service) and 

they said "go to a backup"!!!



I now have another customer who has had the same problem. My other option 

is to move to SQL server.



I cannot understand why Microsoft have no information about this.



At least it's good that I now know I am not alone and going mad!  Best of 

luck.



Alan Hawkins

On more than one occasion, this bug has threatened several days work and 

thousands of records in my office. Here's a workaround discovered by our 

MIS director after we had all worked for hours trying at least save the 

tables:

Open Excel 2000 and import the tables from Access one at a time (Data/Get 

External Data). Open the latest backup version of your database. Import 

the data from Excel, replacing the existing tables so you'll have the 

latest data changes. 

If you've made structural changes since the last backup or modified forms 

or reports, your changes will be lost, but at least you can salvage your 

records. 



> > > > I have written an application that was upgraded from V97 to 2000 

and 

> > > after 

> > > > some time a crash occurred causing an error message (the longest 

in 

> > > > existence????) to appear stating "The database is in an unexpected 

> > > > state..." and suggesting that the cause was that a DAO 

> CompactDatabase 

> > > > method had been used (it hadn't) and suggesting that the Convert 

> > > Database . . . . etc. 

> _______________________________

> Dear David

> 

> Does this sound familiar . . .

> 

> I have written an application that was upgraded from V97 to 2000 and 

after 

> some time a crash occurred causing an error message (the longest in 

> existence????) to appear stating "The database is in an unexpected 

> state..." and suggesting that the cause was that a DAO CompactDatabase 

> method had been used (it hadn't) and suggesting that the Convert 

Database 

> option on the Tools menu be used (you can't as you can't open it or 

import 

> it). It also suggests recreating the database and just importing the 

> tables and queries. 

> I created a new database from scratch, using Access 2000, with new forms 

> and imported the tables, queries, reports and macros from an earlier 

> backup. I have used no modules and hardly any code as I have used the 

> macros instead.

> This has worked fine for a few weeks and now it has happened again!  At 

> the time a report was being print/previewed.

> 

> I can find no mention of this particular error on the MS Knowledgebase. 

> Have you any information please? 

> 

> It is running on a small NT BackOffice system with NT workstations.

> 

> ____________________

> 

> I have posted this on this site and had no responses. I have sent the 

> question to Woody Access Watch twice with not even an acknowlegement. I 

> have made a chargeable support call to ICL (Microsoft support service) 

and 

> they said "go to a backup"!!!

> 

> I now have another customer who has had the same problem. My other 

option 

> is to move to SQL server.

> 

> I cannot understand why Microsoft have no information about this.

> 

> At least it's good that I now know I am not alone and going mad!  Best 

of 

> luck.

> 

> Alan Hawkins