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.
Dig Deeper on Windows client management
Related Q&A from John Robbins
What is a JAD session? This term is referred to often in job postings and seems like some kind of brainstorm you carry out with a client to define IT... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.