Uh-oh. App developed in A2003 won't run in A2000

A

aardvick

Big problem: the app I'm developing runs beautifully on my laptop
(Vista/Office 2003). But today I moved it to my client's network and it is
totaly crippled! Even basic functionality like switching a form to design
view won't work. Any recommendations for where to start reading up on the
differences between versions and how to recover frrom this mess?
Much thanks in advance!
 
D

Dirk Goldgar

aardvick said:
Big problem: the app I'm developing runs beautifully on my laptop
(Vista/Office 2003). But today I moved it to my client's network and it
is
totaly crippled! Even basic functionality like switching a form to design
view won't work. Any recommendations for where to start reading up on the
differences between versions and how to recover frrom this mess?
Click to expand...

That doesn't sound normal to me. You shouldn't have such major problems
unless your database file is in the Access2002-2003 file format, in which
case I wouldn't expect A2K to be able to read it at all.

Are you sure your problems aren't caused by VBA being disabled due to your
database now being blocked or in an untrusted location?

It's also quite likely that you'd have to fix the references in a database
that is being run in a lower version of Access. Have you tried opening the
database, opening the VB Editor environment, clicking Tools ->
References..., and making sure there are no missing references and all
references are set to the appropriate version for this new installation?
 
D

david

That sounds more like an Access 2000 problem than a 2003
problem.

In the sense that Access 2000 had a lot of problems. Make sure
all service packs are applied.

Then check all references by disconnecting any startup code,
decompiling on the 2000 machine, and immediatly opening and
refreshing the references, (by adding any new reference, then
deleting).

(david)
 
A

aardvick

Thanks so much for your reply, Dirk.
I would like to "fix the references." When I open the DB on my cliient's
machine the same 5 references are checked, except that the MS Access Object
Library is 9.0 instead of 11.0. The DAO Object Library is 3.6 for both of
them.
Now what?
Your help is much appreciated!
-aaardvick
 
A

aardvick

Yes, the have sp3 installed.

Chris O'C via AccessMonster.com said:
I pray your client installed Office 2000 SP 3 before you opened the db on his
system. If not, you'll need your backup. The code in the db is history.
The VBE6.dll file is incompatible with Access 2003 VBA, and SP 3 fixes it.

Chris
Microsoft MVP
Click to expand...
 
A

aardvick

Thanks for your reply David! I would like to try what you suggest, but I'm
not sure I understand everything you suggested.

Here is what I've done so far: I went to Tools, Startup... and removed my
switchboard form from the "Display Form/Page" drop down. Display Database
Window and Display Status Bar are unchecked. Then I closed the database and
reopened it.

I don't know what you mean by decompiling. How do I do that?

Then I went to the VB window and clicked on Tools, References... The same 5
are checked as on my machine (except that the Access Object Library is 9.0
instead of 11.0).

So then how do I "refresh" the References? And you mention adding new
reference and then deleting. I'm not sure what you mean. Could you explain
a bit more?

Thanks so much for your help!
-Aardvick
 
Top