Moving from 16-bit Access to 32-bit

My question is how can I find information on the differences of Visual Basic code specification between Access Version 2 and 2000. The database used is Access v2.0 to 2000. I changed all USER to USER32 in declaration. Then I get an error message such as Run-time Error "453" -- Can't find DLL entry point GetClassName in user32. I tried Import Method to import each part of the old version database into Access 2000. I ran into the same problem as User Defined Type Not Defined and "overflow" when I tried running form.
There used to be some documents on the MSDN Library that talked about porting from 16-bit Access to 32-bit Access. However, it looks like they have fallen off since most people have already ported over by now. If you can get your hands on some MSDN Library CD's from 1997-1998, you might find the information. What you are running into is the exported API names from DLLs are slightly different under Win32. If the API takes a string, the API name is either xxxA or xxxW. The A stands for ANSI and the W is the wide or UNICODE version. Win32 on Windows NT/2000 is full UNICODE so Microsoft had to find a way to differentiate the names. It is all done through macros in C/C++ programming. In the case of GetClassName, the real name for your purposes is GetClassNameA. I don't know if they are available but there used to be some programs from third party vendors that would assist you in porting VBA programs from 16 to 32-bit. Check out Visual Basic Programmer's Journal or Office Advisor magazines as those cover VB/VBA programming.

This was first published in April 2001

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.
    Back to top