VBA XP - VBA 2000

  • Thread starter Thread starter Jonathan Blitz
  • Start date Start date
J

Jonathan Blitz

I have built an access project in XP but using Access 2000 database format.
The project includes alot of VBA code.

When I tried to run it on computers that use Office 2000 I find that the VBA
code breaks.
It appears that the version of VBA is not the same and that the code I have
built is not compatable. Re-writing the code is not a good idea.

When I open Help --> about in the VBA window it says I have VB version 6.3.
The computers using Office 2000 have version 6.0.

Is there any (safe) way to update the VB version on those computers without
having to perform a full install of Office XP?

--
Jonathan Blitz
AnyKey Limited
Israel

"When things seem bad
Don't worry and shout
Just count up the times
Things have worked themselves out."
 
It would helped if you had mentioned some of the commands, or code that does
not work. There is little, if any differences I am aware in available
commands.

When you do a save and compile of you code on access 2002 pc, does your code
safely, and correctly compile? (it is for this reason, you should distribute
a mde, as it ensures all your code has NO compile errors). However, a2002
can edit, and create a2000 files, it CAN NOT create a a2000 mde file (which
is what any developer who has had any amount of experience in ms-access
should be doing). In your case, you might have to move the mdb file to a pc
with a2000 on it, and then create the mde file for distribution. It would be
at this time you no doubt do a lot of testing, and your quality control
teams can try and break things BEFORE you distribute to your users.

As mentioned, I am NOT aware of any VB functions that don't exist in a2000
as compared to a2002. I would certainly do a lot of testing on the a2000
pc's before deployment. In fact, you probably should be developing on the
same version anyway. All the little problems,a nd things that you run into
during development can go a long way to making sure that the final product
runs well. You are running, testing, developing on a complete different
system then what the target pc's will be.

However, you also could very well have a broken ref problem. If very old and
common commands like left$, or mid$ is broken, then we talking about
commands that have been present,and compatible for about 10 years in
ms-access.

If these very old and long lived commands don't work, then you are likely
dealing with a refs problem:

Allen Browne
http://users.bigpond.net.au/abrowne1/ser-38.html

Doug Steele:
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

Peter Walker:
http://www.papwalker.com/dllhell/index-page2.html


MsKb Articles: 310803, 208218, 209849, 286300

ACC2000: How Access 2000 Resolves Visual Basic for Applications References
http://support.microsoft.com/default.aspx?scid=kb;en-us;248941

ACC2000: How to Resolve Reference Issues in an Access Database
http://support.microsoft.com/default.aspx?scid=kb;en-us;310803
 
Hi Jonathan,

Thank you for using MSDN Newsgroup! It's my pleasure to assist you with this issue.

I'm amazing that Albert has provided such integrated and valued suggestions on your issue
.. Based on my experience, a MDE file is a better and safer choice in your scenario. I'm here
willing to be of assistance and see if there is anything I can assist you further.

I'm not sure what causes the VBA code broke, however, the most possible cause is the
VBA references issue. Please follow Albert's suggestions and see if the problem still exists.
If it does, we'd better further narrow down it with the following steps (please back up the
database first):

=======================
Import the Objects Directly
=======================
1. Start Microsoft Access 2000, Create a new, blank database.
2. On the File menu, point to Get External Data, and then click Import.
3. Select the 2002 database and then click Import.
4. Select all the objects on each tab of the Import dialog box.
5. Click the Options button, Select the options to import Relationships, "Menus and
Toolbars", and Import/Export Specs.
6. Click OK to perform the import.
7 Recompile the VBA project and add some necessary libraries.


=========================================
Apply Jet 4.0 SP8 and Check for MDAC Version
=========================================

Additoinally, it is recommended that you obtain the latest Jet4.0 Service Pack 8 and
apply it in advance. I also suggest you check your MDAC version and compare the version
umber of each MDAC DLL file to a list of the DLL files that are shipped with each MDAC
version to see if there is any mismatch on the DLLs.

829558 Information About Jet 4.0 Service Pack 8
http://support.microsoft.com/?id=829558

301202 HOW TO: Check for MDAC Version
http://support.microsoft.com/?id=301202

For further information on how to resolve the VBA references problems, please read the
following KB which handles most references issues.

248941 ACC2000: How Access 2000 Resolves Visual Basic for Applications
http://support.microsoft.com/?id=248941

Jonathan, if there is anything more I can do to assist you, please feel free to let us know.
Thanks again for using MSDN Newsgroup!

Best regards,

Billy Yao
Microsoft Online Support
 
Back
Top