Access2000 db bombing in Access 2002

[TKD]

I have recently moved my Access 2000 database to an XP
machine that has both Access 2000 and Access 2003 loaded
on it. I recompiled the Access 2000 database in Access
2000 to incorporate a change and the database works fine
in both Access 2000 and Access 2003. I sent the file to
another XP machine that only has Access 2002 on it and it
bombed. Tried another machine with Access 2002 on it and
same results - initial form comes up but command buttons
don't always work and have a default date field (form has
=Date()) shows "?Name" on the form instead of the date.
Everything works in versions 2000 and 2003 - not in Access
2002. I've brought the database into Access 2003 and
converted it to the 2002/2003 format and again - works in
2003 but not in 2002.

Any ideas????

 

[GVaught]

Any time you move one version of Access to another version, you must always
check that the Access version has the same references set as the original
machine. Most failures are due to not using DAO but ADO or vice versa.

 

[TKD]

I understand that it might be a reference causing the
problem but am not sure how to check it (I don't have the
Access 2002 machine nearby). If I look on my machine
(with the Access 2000 or Access 2003) I can go to the
Visual Basic window and see what I have checked...since
the Access 2002 machine is only running the database from
the forms and not compiling, etc... it should have the
correct references - maybe not the correct versions??? Do
I need to have the person on the Access 2002 machine look
up each associated reference file and see which versions
that they have??

I know that the code references Word and Excel (for
exports) in Office 2003 (shows as 11.0 in the
references). Clearly the Office 2002 machine only has
version 10.0 - however, the database isn't bombing at the
exports...it's having problems everywhere. The other
references are the standard "VB for applications", "Access
9.0" (lowest common denominator), "OLE automation", "VB
extension 5.3" and "ActiveX Data Objects 2.1"....

Anyone know of any particular mess up with Access 2002 and
these references?

 

[Douglas J. Steele]

You can only refer to Access 9.0 if you're using Access 2000. Access 2003
MUST refer to Access 11.0 (and Access 2002 MUST refer to Access 10.0)

 

[TKD]

This is an Access 2000 database. Data entry is just
sometimes done with a machine that has Access 2003 or
Access 2002 on it. Until I move this over to the new
machine that also had Access 2003 on it, the people doing
data entry on a Access 2002 machine didn't have any
problems. They could bring up the Access 2000 database
and run it just fine. Now, it bombs (but only on the
Access 2002 machines, not on the Access 2003 machines).

 

[Douglas J. Steele]

Hopefully your application is split into a front-end (containing the
queries, forms, reports, macros and reports), linked to a back-end
(containing just the tables). The back-end should be in Access 2000 format,
and should be on the server. You should have a different version of the
front-end for each version of Access involved, and each user should have the
version appropriate to whatever version of Access they have (and it should
be on their harddrive). That way, you can have the correct references.

 

[Tony Toews]

I know that the code references Word and Excel (for
exports) in Office 2003 (shows as 11.0 in the
references).

Use Late Binding then.

Clearly the Office 2002 machine only has
version 10.0 - however, the database isn't bombing at the
exports...it's having problems everywhere.

This is typical behavior. One bad apple and all applies to references.

Late binding means you can safely remove the reference and only have
an error when the app executes lines of code in question. Rather than
erroring out while starting up the app and not allowing the users in
the app at all. Or when hitting a mid, left or trim function call.

You'll want to install the reference if you are programming or
debugging and want to use the object intellisense while in the VBA
editor. Then,. once your app is running smoothly, remove the
reference and setup the late binding statements.

Sample code:
' Declare an object variable to hold the object
' reference. Dim as Object causes late binding.
Dim objWordDoc As Object
Set objWordDoc = CreateObject(" Word.Document")

For more information including additional text and some detailed links
see the "Late Binding in Microsoft Access" page at
http://www.granite.ab.ca/access/latebinding.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm