2002 vs 2003

[AJ]

I wrote a database in 2003 with tables, vba modules, etc. I am having someone
run it who I think has access 2002 and he is getting all types of errors.
I wanted him to remove the digital signature but it does not exist in the
visual basic editor,tools. Also, under the main access window under tools,
macro, he does not have a security field?
Are 2002 and 2003 not compatible. Is there anything he can do other then
install 2003? Any ideas? Has anyone ever faced this before?
Most of the errors are saying the modules are locked or he gets a compile
error when trying to run the application.

 

[Allen Browne]

Presumably you created an Access 2002/3 file format MDB, and compiled it
into an MDE using Access 2003.

If so, it will not work under A2002. Although the file format is the same
the binary (compiled VBA code) is different in every version of Access. They
are backwards compatible, but not forward compatible. So, A2003 can use an
MDE created in A2002, but A2002 cannot use an MDE created in A2003.

The nonsense security warnings were only introduced in A2003. Consequently,
there is no menu item in A2002 to change the macro security level.

So, other than him installing A2003, your option is for you to install A2002
and create the MDE under that version.

If you prefer, you could convert the mdb to A2000 format, and release the
MDE under Access 2000, and it will work on A2000, A2002, A2003, and A2007
machines.

 

[AJ]

Allen I am very confused. I have office 2003 but when I went to make a MDE
file it states that I have to convert the database to 2003? Why would it have
created in 2000 when I have 2003? (I assume that is what I did because when I
go to connvert the database, I can convert to 2003 or 97 (the 2000 format is
grayed out).)
Then I send him the 2003 version and he cannot use it and gets all types of
errors. (Even if I send the MDB version.)
Any ideas on how to resolve this? SHould I have him upgrade? Did I do
something wrong that it created the database in 2000 even though I have 2003

 

[Allen Browne]

You cannot create an Access 2000 MDE by using Access 2003.

You can create an Access 2002/3 MDE using Access 2003, but it will then be
usable in A2003 only (not A2002.)

If you are talking about an MDB, you could try decompiling and sending him
the decompiled version. His A2002 will then compile it on the fly. For this
to work you would need to be certain that you have not used any references
that are not on his machine. For example, it won't work if you have
references to MS Calendar, MS Graph, MS Outlook 11, etc.

If you are not sure about library references, see:
http://allenbrowne.com/ser-38.html

The process to decompile would be like this:
1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database:
Tools | Database Utilities | Compact/Repair

3. Close Access. Make a backup copy of the file. Decompile the database by
entering 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"

4. Open Access (holding down the Shift key if you have any startup code),
and compact again.

5. Make a copy of the file in this state (i.e. while NO code has run), and
send him this copy.