Differences between A2K and A02

[Mark]

I'm using A2002 on an A2K mdb however many of my A2K users are getting
fatal compiler errors because I'm using functions and arguments that are
not in A2K.

1. How do I set up my A02 so that the VBA editor won't compile non-A2K
functions or arguements?

2. Is there a way (like through the object browser) to tell which
functions/arguments are available in A2K?

3. Is there a comprehensive list somewhere to reference available
functions and arguments?

TIA

Mark

 

[Peter R. Fletcher]

By default, A2002 uses the A2K file format, and there are few, if any,
internal VBA Functions that are new in A2002 - I have supported users
with A2K using applications developed in A2002, and certainly have not
run into any unsupported Functions. The new features of A2002 do
include new Form, Report, and Control Properties, two new Form types,
a fair number of changes to Table handling and SQL, and a number of
features related to the use of Access databases on the intra- and
internet.

The problems that your users are encountering are almost certainly due
to Reference problems. Your application will almost certainly be
referring to subsidiary Office 2002 libraries which don't exist (of
course) on a system with only Office 2000 installed. When your
applications are transferred to the systems with the older version of
Office, you will find that you need to replace any references that
show up as "missing" in Tools|References in the VB Editor with the
corresponding library from the Office 2000 installation (Excel for
Excel, Word for Word, etc.).

I'm using A2002 on an A2K mdb however many of my A2K users are getting
fatal compiler errors because I'm using functions and arguments that are
not in A2K.

1. How do I set up my A02 so that the VBA editor won't compile non-A2K
functions or arguements?

2. Is there a way (like through the object browser) to tell which
functions/arguments are available in A2K?

3. Is there a comprehensive list somewhere to reference available
functions and arguments?

TIA

Mark

Please respond to the Newsgroup, so that others may benefit from the exchange.
Peter R. Fletcher

 

[Mark]

Peter,

Thank you for your response. What libraries should I use as references
to force it to A2K? Right now I'm referencing VBA6.

TIA,
Mark

 

[Peter R. Fletcher]

I am sure that you have more References than that! Even a minimal
A2002 application will be referencing the relevant Access Library,,
the VBA library (which doesn't have a version number in A2002), the
OLE Automation Library, and an ActiveX Data Objects Library. These
references _should_, however, be correctly "translated" by the older
Access version. You may well also be referencing a DAO library (if you
are using DAO Properties in any of your code), the Microsoft Office
Object Library, and/or others. It is these latter references that are
likely to be broken when you try to move the application to A2K. What
you need to do is open the application (without running any startup
code) on the problem systems, see what references are broken, delete
them, and find corresponding older libraries on the list to replace
them.

Peter,

Thank you for your response. What libraries should I use as references
to force it to A2K? Right now I'm referencing VBA6.

TIA,
Mark

Please respond to the Newsgroup, so that others may benefit from the exchange.
Peter R. Fletcher

 

[Brendan Reynolds]

As Peter says elsewhere in this thread, it's unlikely that the problem lies
in the VBA library. Access 2000, Access 2002, and Access 2003 all use the
VBA 6 library (there isn't, and probably now never will be, any later
version of VBA). There are, however, new methods added to some of the
objects in the Access object library in recent versions. For example, if I
remember correctly, I believe that the AddItem and RemoveItem methods were
added to the Access combo box control in Access 2002, so you will get errors
if you attempt to use those methods in Access 2000.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.