469,924 Members | 1,492 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,924 developers. It's quick & easy.

Access 2000 files with Access 2003

Hello,

I have an Access 2000 database that I copied to a new computer with Access
2003. Access 2003 says the file is in Access 2000 file format. I made some
changes to the Access 2000 file code on the computer with Access 2003, and
compiled. I copied the file back to the Access 2000 machine and the file
runs, but the code is unviewable. Any ideas on why this happens?

Mike G.
Nov 13 '05 #1
3 2221
Access 2003 can work with Access 2000 files, but it uses a different binary
(compiled format). If you then go back to Access 2000, it is supposed to
just recompile and keep going. Unfortunately this does not work reliably,
and corruptions like the one you describe are fairly frequent.

Run a decompile before you switch versions. First make a copy of the mdb (in
case something goes wrong). Then enter something like this at the command
prompt while Access is not running. It is all one line, and include the
quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

Then compact the database, and you should find this works okay in the other
version. Repeat that process when coming the other way again. When
decompiling, use the version of msaccess that you have been editing with.

For other tips on avoiding corruptions, see:
Preventing Corruption
at:
http://members.iinet.net.au/~allenbrowne/ser-25.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Mike Gramelspacher" <gr******@psci.net> wrote in message
news:cn**********@pscinews.psci.net...

I have an Access 2000 database that I copied to a new computer with Access
2003. Access 2003 says the file is in Access 2000 file format. I made
some changes to the Access 2000 file code on the computer with Access
2003, and compiled. I copied the file back to the Access 2000 machine and
the file runs, but the code is unviewable. Any ideas on why this happens?

Mike G.

Nov 13 '05 #2
Thanks, Allen. I see now that I omitted an important fact. The Message box
title was Project Locked. I had signed it using a digital certificate made
with Selfcert.exe. That was probably the problem all along. A signed
project apparently cannot be decompiled. Anyway, I finally realized what
was wrong, removed the digital certificate and followed your instructions.
Now the code is editable on the Access 2000 machine. I learned a lot from
this problem. Too bad I have to always learn everything the hard way.

Mike
Nov 13 '05 #3
Thanks for posting the solution, Mike.

Another good example of why the macro security nonsense in A2003 causes more
problems that it solves.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Mike Gramelspacher" <gr******@psci.net> wrote in message
news:cn**********@pscinews.psci.net...
Thanks, Allen. I see now that I omitted an important fact. The Message
box title was Project Locked. I had signed it using a digital certificate
made with Selfcert.exe. That was probably the problem all along. A
signed project apparently cannot be decompiled. Anyway, I finally
realized what was wrong, removed the digital certificate and followed your
instructions. Now the code is editable on the Access 2000 machine. I
learned a lot from this problem. Too bad I have to always learn
everything the hard way.

Mike

Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

17 posts views Thread by chicha | last post: by
1 post views Thread by Wayne Aprato | last post: by
6 posts views Thread by Peter Frost | last post: by
28 posts views Thread by Neil Ginsberg | last post: by
3 posts views Thread by banba_ca | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.