DAO Error - microsoft.public.access.conversion

Hi, When I open up my access database I get this error. Error1: The database was created in an earlier version of Microsoft Access. To convert the database to the current version of Microsoft Access, close the database, point to DB Utilities on the Tools menu and then click convert database. After I do this, I then receive this error. " Microsoft Access There were compilation errors during conversion or enabling of this database. This might be due to old DAO syntax that is no longer supported. For an example on how to fixup the code, click HELP." Your help is appreciated. Thanks, Rachel

Rachel wrote: > After I do this, I then receive this error. > > " Microsoft Access > There were compilation errors during conversion or > enabling of this database. This might be due to old DAO > syntax that is no longer supported. For an example on how > to fixup the code, click HELP." Go into any module (or just hit Ctrl-G). Go to Tools, References and look at the references that are checked. If any are marked missing, uncheck them. Ensure that DAO 3.6 library is checked. Then go to Debug, and click on Compile, then click on the save button. -- Joan Wild Microsoft Access MVP

Hi, I followed your instructions but I receive the same error after making the changes. There were no references missing but compiling the program raised an error. strdate.date I changed the code to datetime and then it compiled without any problems. But then I was unable to save. Access told me that I would basically have to convert the database first and then I could make changes to it. So I converted, changed the code and recompiled and received no errors. After this, I tried running the reports and they all show up as errors. Any other ideas? Thanks, Rachel >-----Original Message----- >Rachel wrote: >> After I do this, I then receive this error. >> >> " Microsoft Access >> There were compilation errors during conversion or >> enabling of this database. This might be due to old DAO >> syntax that is no longer supported. For an example on how >> to fixup the code, click HELP." > >Go into any module (or just hit Ctrl-G). Go to Tools, References and look >at the references that are checked. > >If any are marked missing, uncheck them. Ensure that DAO 3.6 library is >checked. > >Then go to Debug, and click on Compile, then click on the save button. >-- >Joan Wild >Microsoft Access MVP > > >. >

What version of Access are you converting from and to? I expected you to convert and then follow the steps. What references do you have checked? Rachel wrote: > Hi, > I followed your instructions but I receive the same error > after making the changes. > There were no references missing but compiling the program > raised an error. strdate.date > I changed the code to datetime and then it compiled > without any problems. > But then I was unable to save. Access told me that I would > basically have to convert the database first and then I > could make changes to it. > So I converted, changed the code and recompiled and > received no errors. > After this, I tried running the reports and they all show > up as errors. > > Any other ideas? > > Thanks, > Rachel >> -----Original Message----- >> Rachel wrote: >>> After I do this, I then receive this error. >>> >>> " Microsoft Access >>> There were compilation errors during conversion or >>> enabling of this database. This might be due to old DAO >>> syntax that is no longer supported. For an example on how >>> to fixup the code, click HELP." >> >> Go into any module (or just hit Ctrl-G). Go to Tools, References >> and look at the references that are checked. >> >> If any are marked missing, uncheck them. Ensure that DAO 3.6 >> library is checked. >> >> Then go to Debug, and click on Compile, then click on the save >> button. -- >> Joan Wild >> Microsoft Access MVP >> >> >> . -- Joan Wild Microsoft Access MVP

Hi, I am converting to Access 2000. Here is the list of references selected. Visual Basic For Applications Microsoft Access 9.0 Object Library Ole Automation utility Microsoft Visual Basic or Applications Extensibility 5.3 Microsoft DAO 3.6 Object Library Rachel >-----Original Message----- >What version of Access are you converting from and to? I expected you to >convert and then follow the steps. > >What references do you have checked? > >Rachel wrote: >> Hi, >> I followed your instructions but I receive the same error >> after making the changes. >> There were no references missing but compiling the program >> raised an error. strdate.date >> I changed the code to datetime and then it compiled >> without any problems. >> But then I was unable to save. Access told me that I would >> basically have to convert the database first and then I >> could make changes to it. >> So I converted, changed the code and recompiled and >> received no errors. >> After this, I tried running the reports and they all show >> up as errors. >> >> Any other ideas? >> >> Thanks, >> Rachel >>> -----Original Message----- >>> Rachel wrote: >>>> After I do this, I then receive this error. >>>> >>>> " Microsoft Access >>>> There were compilation errors during conversion or >>>> enabling of this database. This might be due to old DAO >>>> syntax that is no longer supported. For an example on how >>>> to fixup the code, click HELP." >>> >>> Go into any module (or just hit Ctrl-G). Go to Tools, References >>> and look at the references that are checked. >>> >>> If any are marked missing, uncheck them. Ensure that DAO 3.6 >>> library is checked. >>> >>> Then go to Debug, and click on Compile, then click on the save >>> button. -- >>> Joan Wild >>> Microsoft Access MVP >>> >>> >>> . > >-- >Joan Wild >Microsoft Access MVP > > >. >

You should be able to uncheck the utility one. Then go to Debug, Compile. If you get any errors, you'll need to fix them. If it compiles, then hit the save button. Close the window and then go to Tools, Database Utilities, Compact. -- Joan Wild Microsoft Access MVP

"Rachel" <Rachel@hotmail.com> wrote in message news:250b01c50d33$128dc020$a401280a@phx.gbl... > Hi, > When I open up my access database I get this error. > > Error1: > The database was created in an earlier version of > Microsoft Access. To convert the database to the current > version of Microsoft Access, close the database, point to > DB Utilities on the Tools menu and then click convert > database. > > After I do this, I then receive this error. > > " Microsoft Access > There were compilation errors during conversion or > enabling of this database. This might be due to old DAO > syntax that is no longer supported. For an example on how > to fixup the code, click HELP." > > Your help is appreciated. > > Thanks, > Rachel

Similiar Articles:

DAO TableDef error - microsoft.public.access.formscoding ...
I must be having a brain cramp. The following code is generating a run-time error 3420: Object invalid or no longer set. The line that is marked wi...

unexpected state DAO error message - microsoft.public.access ...
I had this message with only one user in a workgroup - a new one. After much troubleshooting found the user had no groups - not even 'user' to his name.

DAO Database execute get too few parameter - microsoft.public ...
unexpected state DAO error message - microsoft.public.access ..... file and you should get a message ... Run-time error 3061; Too few parameters. ...

Runtime Error: 3146 - microsoft.public.access
While trying to add new > record, I received the Runtime Error 3146. > > Dim varObjectid As Long > Dim dbs As DAO.Database > Dim rstObject As DAO.Recordset > Set dbs ...

Unrecognized database format - microsoft.public.access
If you happened to pick the Microsoft DAO 3.51 Object Library, then you can only ... However, I keep > getting... > > Run-time error '3343'" Unrecognized database format ...

Error opening database - microsoft.public.access
You need to use DAO 3.6 for databases created using Access 2003. -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no private e-mails, please) "Rotsey ...

'asctrls.ocx' error - microsoft.public.access
unexpected state DAO error message - microsoft.public.access ... asctrls.ocx error - microsoft.public.access unexpected state DAO error message - microsoft.public.access ...

Run-time error 3061; Too few parameters. Expected 2 - microsoft ...
Private Sub Sect_BeforeUpdate(Cancel As Integer) Dim db As dao.Database Dim rst As dao.Recordset Set rst = CurrentDb.OpenRecordset("Select * Fr...

Access 2007 Error in Loading DLL Revisited - microsoft.public ...
There were DAO problems and some minor stuff with editing and adding records, But ... I checked the event viewer and there appears an error report in the Application log ...

Compile error on OpenQueryDef - microsoft.public.access ...
Why do I get a compile error on OpenQuerydef? It saids "Function or interface marked ... SendMessage() >> > Dim qdf As DAO.QueryDefs >> > Dim rsRecip As DAO ...

Error Object (DAO)
Error object contains details about data access errors, each of which pertains to a single operation involving DAO.

DAO error: During Install - Vesper Software - Vesper Software, LLC
DAO error: During Install. There is a 3rd party installation program out there corrupting the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared ...

Help for Common Microsoft Access DAO Error Messages
This is one of the more common errors experienced by Access users. Contact us to eliminate this problem properly. Need to compare Access tables in 2 different databases?

Trappable Microsoft Jet and DAO Errors [Access 2007 Developer ...
Code: Message: 2420: Syntax error in number. 2421: Syntax error in date. 2422: Syntax error in string. 2423: Invalid use of '.', '!', or '()'. 2424: Unknown name.

DAO Error List in Database Reference Forum
3000 Reserved error ( ); there is no message for this error. 3001 Invalid argument. 3002 Couldn't start session. 3003 Couldn't start transaction; too many ...

7/20/2012 7:21:40 AM