|
 |
access thread: Re: Unexpected State - DAO error message
Message #1 by Susie.Eades@a... on Fri, 18 May 2001 17:10:20
|
|
> 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. A graphic of the entire message box is available!
>
> 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.
>
> It is running on a small NT BackOffice system with NT workstations.
>
> Has anyone any ideas please!
Message #2 by Susie.Eades@a... on Fri, 18 May 2001 17:29:55
|
|
Have you found out what caused this? I just had the exact same thing
happen, except was not even able to import anything into a new 2000
database! I did convert from 97 to 2000 using the Convert Database
command on the Tools menu, so am wondering if the Microsoft message be the
wrong one for whatever the problem is. I can create another one using an
older copy, but a lot of data had been added to the converted db, forms
had been changed, etc and would be a lot of work. Problem is, if it
happened to you a 2nd time using a new 2000 database, it seems likely it
could happen to mine again as well--this isn't doing a lot for the
confidence level of my users!
Have created many complex Access 97 applications and have never seen this
happen. Please let me know if you know what caused this or how to keep it
from happening again. Have you had any more trouble with it or did you go
to a different kind of database? I'm also running on NT--my db is on a
LAN and users are on NT workstations--could NT be an issue?
If anyone has any ideas, I'd really appreciate your input! Thanks!!
----------------------------------------------------------------------
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. A graphic of the entire message box is available!
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.
It is running on a small NT BackOffice system with NT workstations.
Has anyone any ideas please!
Message #3 by "Pardee, Roy E" <roy.e.pardee@l...> on Fri, 18 May 2001 09:35:02 -0700
|
|
Have a look at
http://support.microsoft.com/support/kb/articles/Q209/1/37.ASP
Particularly the "typical causes of .mdb file corruption" bit at the end.
HTH,
-Roy
-----Original Message-----
From: Susie.Eades@a... [mailto:Susie.Eades@a...]
Sent: Friday, May 18, 2001 10:09 AM
To: Access
Subject: [access] Re: Unexpected State - DAO error message
> 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. A graphic of the entire message box is available!
>
> 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.
>
> It is running on a small NT BackOffice system with NT workstations.
>
> Has anyone any ideas please!
Message #4 by Madhu Mopuri <MMopuri@c...> on Fri, 18 May 2001 13:16:18 -0400
|
|
It worked. The problem was there was a space(& history)between & and
variable in the link. That caused the problem.
thanks,
Madhu
<a href = 'EHDetail.asp?EquipID=" & Equip & "& history="&
rs5.Fields(6).value &"'>
> -----Original Message-----
> From: Susie.Eades@a... [SMTP:Susie.Eades@a...]
> Sent: Friday, May 18, 2001 1:10 PM
> To: Access
> Subject: [access] Re: Unexpected State - DAO error message
>
> > 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. A graphic of the entire message box is available!
> >
> > 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.
> >
> > It is running on a small NT BackOffice system with NT workstations.
> >
> > Has anyone any ideas please!
>
Message #5 by "Susie Eades" <Susie.Eades@a...> on Fri, 18 May 2001 12:35 -0500
|
|
I have been searching Microsoft most of the morning, with no luck, but hadn't
come across this one yet--thanks! It'll take a while to go through all the
suggestions it lists, but will get started and see what happens. Thanks for
your help!
Susie
____________________Reply Separator____________________
Subject: [access] Re: Unexpected State - DAO error message
Author: access@p...
Date: 05/18/2001 11:35 AM
Have a look at
http://support.microsoft.com/support/kb/articles/Q209/1/37.ASP
Particularly the "typical causes of .mdb file corruption" bit at the end.
HTH,
-Roy
-----Original Message-----
From: Susie.Eades@a... [mailto:Susie.Eades@a...]
Sent: Friday, May 18, 2001 10:09 AM
To: Access
Subject: [access] Re: Unexpected State - DAO error message
> 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. A graphic of the entire message box is available!
>
> 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.
>
> It is running on a small NT BackOffice system with NT workstations.
>
> Has anyone any ideas please!
Message #6 by "Oliver Dempsey" <odempsey@b...> on Mon, 21 May 2001 08:58:42 +0100
|
|
Hi Susie
how much space is left on your hard drive. I've seen Access databases get
destroyed when the hard drive was nearly full. Records mysteriously
disappeared and got mixed up.
That's all I can think of.
Regards
Oliver
----- Original Message -----
From: Susie Eades <Susie.Eades@a...>
To: Access <access@p...>
Sent: Friday, May 18, 2001 6:35 PM
Subject: [access] Re:Re: Unexpected State - DAO error message
> I have been searching Microsoft most of the morning, with no luck, but
hadn't
> come across this one yet--thanks! It'll take a while to go through all
the
> suggestions it lists, but will get started and see what happens. Thanks
for
> your help!
> Susie
>
> ____________________Reply Separator____________________
> Subject: [access] Re: Unexpected State - DAO error message
> Author: access@p...
> Date: 05/18/2001 11:35 AM
>
> Have a look at
>
> http://support.microsoft.com/support/kb/articles/Q209/1/37.ASP
>
> Particularly the "typical causes of .mdb file corruption" bit at the end.
>
> HTH,
>
> -Roy
>
> -----Original Message-----
> From: Susie.Eades@a... [mailto:Susie.Eades@a...]
> Sent: Friday, May 18, 2001 10:09 AM
> To: Access
> Subject: [access] Re: Unexpected State - DAO error message
>
>
> > 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. A graphic of the entire message box is available!
> >
> > 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.
> >
> > It is running on a small NT BackOffice system with NT workstations.
> >
> > Has anyone any ideas please!
>
>
>
>
Message #7 by "Susie Eades" <Susie.Eades@a...> on Mon, 21 May 2001 16:37 -0500
|
|
Hi Oliver,
I have 11.9 gig on my d:\, but my c:\ (where where Office is installed) has only
152 mg. The database is on the LAN, so I didn't think space would be a problem.
Now that you mention it, however, the afternoon that this happened, there was a
message from LAN saying that drive was full--you could have solved the
mystery--maybe that's exactly what happened! In researching some more, it looks
like maybe the code could be a problem also. Apparently, 97 used DAO 3.5 and
2000 only supports 3.6. Do you know anything about that?
Susie
____________________Reply Separator____________________
Subject: [access] Re:Re: Unexpected State - DAO error message
Author: access@p...
Date: 05/21/2001 2:58 AM
Hi Susie
how much space is left on your hard drive. I've seen Access databases get
destroyed when the hard drive was nearly full. Records mysteriously
disappeared and got mixed up.
That's all I can think of.
Regards
Oliver
----- Original Message -----
From: Susie Eades <Susie.Eades@a...>
To: Access <access@p...>
Sent: Friday, May 18, 2001 6:35 PM
Subject: [access] Re:Re: Unexpected State - DAO error message
> I have been searching Microsoft most of the morning, with no luck, but
hadn't
> come across this one yet--thanks! It'll take a while to go through all
the
> suggestions it lists, but will get started and see what happens. Thanks
for
> your help!
> Susie
>
> ____________________Reply Separator____________________
> Subject: [access] Re: Unexpected State - DAO error message
> Author: access@p...
> Date: 05/18/2001 11:35 AM
>
> Have a look at
>
> http://support.microsoft.com/support/kb/articles/Q209/1/37.ASP
>
> Particularly the "typical causes of .mdb file corruption" bit at the end.
>
> HTH,
>
> -Roy
>
> -----Original Message-----
> From: Susie.Eades@a... [mailto:Susie.Eades@a...]
> Sent: Friday, May 18, 2001 10:09 AM
> To: Access
> Subject: [access] Re: Unexpected State - DAO error message
>
>
> > 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. A graphic of the entire message box is available!
> >
> > 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.
> >
> > It is running on a small NT BackOffice system with NT workstations.
> >
> > Has anyone any ideas please!
|
|
|
View Cart
