By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,607 Members | 1,758 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,607 IT Pros & Developers. It's quick & easy.

DAO Compile Error

P: n/a
I've been working with an Access 97 application, through various
versions, for 10 years. This application runs asan mde in runtime mode
on hundreds of PCs around the globe.

About a week ago I started getting frequent corruption in the front
end mdb, followed by compile errors for DAO 3.51 declarations, on my
development PC.

My app starts using a CheckReferences routine, written, I think, by
the Harbin bros. I've been using this routine in this application
since 1999. DAO is still there and the reference is intact.

I import everything into a new database and recompile using /decompile
and the problem goes away ... for a bit.

I have reinstalled Acc97 + SR2. Problem keeps coming back. Any clues?

Thanks

Jennifer
Feb 28 '08 #1
Share this Question
Share on Google+
3 Replies


P: n/a
It may have something to do with computers moving from WindowsVista to
WindowsXP. To check references you generally need to use the ADOX
reference. WindowsVista keeps changing the reference to a newer version.
When the front end is brought back to WindowsXP, the reference is corrupt.

Other than that, it's amazing Access97 still works. That's pretty cool

Dom
"Jennifer" <MX*****@gmail.comwrote in message
news:85**********************************@s13g2000 prd.googlegroups.com...
I've been working with an Access 97 application, through various
versions, for 10 years. This application runs asan mde in runtime mode
on hundreds of PCs around the globe.

About a week ago I started getting frequent corruption in the front
end mdb, followed by compile errors for DAO 3.51 declarations, on my
development PC.

My app starts using a CheckReferences routine, written, I think, by
the Harbin bros. I've been using this routine in this application
since 1999. DAO is still there and the reference is intact.

I import everything into a new database and recompile using /decompile
and the problem goes away ... for a bit.

I have reinstalled Acc97 + SR2. Problem keeps coming back. Any clues?

Thanks

Jennifer

Feb 28 '08 #2

P: n/a
On Feb 28, 1:02*pm, "Dominic Vella" <dominic.ve...@optusnet.com.au>
wrote:
It may have something to do with computers moving from WindowsVista to
WindowsXP. * To check references you generally need to use the ADOX
reference. * WindowsVista keeps changing the reference to a newer version.
When the front end is brought back to WindowsXP, the reference is corrupt.

Other than that, it's amazing Access97 still works. * That's pretty cool

Dom

"Jennifer" <MXRo...@gmail.comwrote in message

news:85**********************************@s13g2000 prd.googlegroups.com...
I've been working with an Access 97 application, through various
versions, for 10 years. This application runs asan mde in runtime mode
on hundreds of PCs around the globe.
About a week ago I started getting frequent corruption in the front
end mdb, followed by compile errors for DAO 3.51 declarations, on my
development PC.
My app starts using a CheckReferences routine, written, I think, by
the Harbin bros. I've been using this routine in this application
since 1999. DAO is still there and the reference is intact.
I import everything into a new database and recompile using /decompile
and the problem goes away ... for a bit.
I have reinstalled Acc97 + SR2. Problem keeps coming back. Any clues?
Thanks
Jennifer- Hide quoted text -

- Show quoted text -
Hello Dominic

Thank you or your input. The runtime version runs happily on both XP
and Vista (thanks to sagekey.com). The development version, where I
have the problem, is only on XP.

Jen
Feb 28 '08 #3

P: n/a
On Feb 28, 1:03*pm, Jennifer <MXRo...@gmail.comwrote:
On Feb 28, 1:02*pm, "Dominic Vella" <dominic.ve...@optusnet.com.au>
wrote:


It may have something to do with computers moving from WindowsVista to
WindowsXP. * To check references you generally need to use the ADOX
reference. * WindowsVista keeps changing the reference to a newer version.
When the front end is brought back to WindowsXP, the reference is corrupt.
Other than that, it's amazing Access97 still works. * That's pretty cool
Dom
"Jennifer" <MXRo...@gmail.comwrote in message
news:85**********************************@s13g2000 prd.googlegroups.com...
I've been working with an Access 97 application, through various
versions, for 10 years. This application runs asan mde in runtime mode
on hundreds of PCs around the globe.
About a week ago I started getting frequent corruption in the front
end mdb, followed by compile errors for DAO 3.51 declarations, on my
development PC.
My app starts using aCheckReferencesroutine, written, I think, by
the Harbin bros. I've been using this routine in this application
since 1999. DAO is still there and the reference is intact.
I import everything into a new database and recompile using /decompile
and the problem goes away ... for a bit.
I have reinstalled Acc97 + SR2. Problem keeps coming back. Any clues?
Thanks
Jennifer- Hide quoted text -
- Show quoted text -

Hello Dominic

Thank you or your input. The runtime version runs happily on both XP
and Vista (thanks to sagekey.com). The development version, where I
have the problem, is only on XP.

Jen- Hide quoted text -

- Show quoted text -
Just in case this is of any use to anyone, the problem is fixed ...
the CheckReferences routine has to be called from autoexec to be
effective. I recently moved it so that it was called from a module.
Once I put it back, the corruption problems went away.

Jen
Mar 7 '08 #4

This discussion thread is closed

Replies have been disabled for this discussion.