The names of intrinsic constants changed, but the Access 2.0 intrinsic
constant names are recognized for backward compatibility, so that is not a
problem.
The differences between Access Basic and VBA have been, in my experience,
few and the modifications needed, obvious.
The major area where you'll have to modify is in your use of the Windows
API, if any. Although the 16-bit API calls, in most cases, will still work
if you run the Access 2.0 code, they are not usable with the converted
(e.g., 32-bit) code. There is some change to the name of [most | all] API
calls between 16- and 32-bit Windows. In my experience, this was in all the
ones I had used, but many of the equivalent 32-bit API calls are illustrated
in examples at
http://www.mvps.org, and others can be found with minimal
effort at searching the archive of this newsgroup at
http://groups.google.com or searching the net. Many other APIs are discussed
in various MVP sites for Visual Basic -- look at
http://www.mvps.org/. Karl
Peterson has an index that covers a wide range of applicable APIs at his
site,
http://www.mvps.org/vb.
In most of the Access 2.0 database applications that I've converted which
did not access the Windows API, they converted without any problem.
Larry Linson
Microsoft Access MVP
"Penn" <pe**@upenn.edu> wrote in message
news:bp***********@netnews.upenn.edu...
Hi,
Has anyone converted from 2.0? Let me know how it went - and if there is
a good reference for converting the code in addition to the database.
- SH
