Access 2000 and Access 2003, can't open VBE for mdb file!

[Franc Sutherland]

Hello everyone,

I have made a system in Access 2003, but in the Access 2000 format, as the
end-user has 2000 on his PC. However, the mdb file is not proving to be very
stable.
It has started to not recognise the date() function, which meant I had to go
through all the queries and VBA changing date() to now(). Also, I had to do
this on my own machine, as I could not access the VB editor for this file
through the Access 2000 programme. To check whether the VBE in the 2000 was
working at all, I created a new database and did ALT = F11, and it was
working fine. For some reason, the VBA project is completely locked in the
file I created using 2003. It is not an MDE file, and I have never saved it
in 2003 version, but, always in 2000 version. Can anyone explain why I can't
get into the VBE when I open the mdb file in the 2000 version?
I would really appreciate your help, this is starting to become a problem.
Many Thanks,
Franc Sutherland.

 

[Scott McDaniel]

Hello everyone,

I have made a system in Access 2003, but in the Access 2000 format, as the
end-user has 2000 on his PC. However, the mdb file is not proving to be very
stable.
It has started to not recognise the date() function, which meant I had to go
through all the queries and VBA changing date() to now(). Also, I had to do
this on my own machine, as I could not access the VB editor for this file
through the Access 2000 programme. To check whether the VBE in the 2000 was
working at all, I created a new database and did ALT = F11, and it was
working fine. For some reason, the VBA project is completely locked in the
file I created using 2003. It is not an MDE file, and I have never saved it
in 2003 version, but, always in 2000 version. Can anyone explain why I can't
get into the VBE when I open the mdb file in the 2000 version?
I would really appreciate your help, this is starting to become a problem.

Not sure why the VBE won't come up, but it could be related to one of the issues you mention ...

Did you use any 2003-specific items (like the Printer object, for example) in your application? The 2000 "format" refers
to the database structure; if you're working on a 2000-format db in Access 2003, there's nothing to stop you from using
2003-specific coding items and such (again, liek the Printer object). This can cause some very odd behavior ...

Have you verified that the app's References are available on the 2000 machine? I know you can't get into the VBE, but
you can jot down the refs, then (on the 2000 machine) open a new, blank db and try to remake those refs ... if they're
not available, then the necessary library is NOT installed on the 2000 machine, and you'll have to either (a) install
the requisite library or (b) do away with the reference.

Finally, you really should test the application in the environment to which it will be deployed. For example, if you
know that you must support Access 2000 on Windows 2000, then you'd be wise to build a test machine/environment that
exactly emulates that and run your application. FWIW, Microsoft is now giving away Virtual PC (search on Virtual PC to
find the link) which you can use to build "virtual machines".

Many Thanks,
Franc Sutherland.

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com