Quote Originally Posted by fafalone View Post
The difficulty really depends on how many APIs you use, whether and what kinds of VB internals hacks you use, and whether you work a lot with pointers. Also if you use any 3rd party ocx or DLL files -- these must be 64bit as well. In the future tB has plans to support 32bit ocxs in 64bit apps, but that's a v2.0 thing so not soon. If you don't have the source and the developer doesn't provide a 64bit build, you may need a replacement.

My WinDevLib project helps a lot. The best approach is to simply comment out all your Windows API defs and let it take over. Yes there's some signature differences as every VB programmer has their own preferences, but I've added overloads and consistent standards to help with that. Mostly it's tedious; you'll then have to go around and change a bunch of Long to LongPtr to fit the new APIs, search for anywhere you might have used pointer math with a hard coded pointer size, etc.

AIs can help, but they're not a replacement for actual programmers doing anything beyond boilerplate with numerous examples online. In particular for this, they tend to struggle with multiple indirection with pointers and catching the dozens of edge cases and gotchas; like it's never gotten it right when faced with a ByVal UDT and the trouble of handling that when VBx/tB can't (tB will at some point but not yet).
Ok fafalon, thanks for the info, now I understand something about where this is going, I already saw how to use your WinDevLib, the AI ??helped me understand, and as my projects are quite simple, I only use VB6 for the graphic design of my programs, everything they really do, I do it with other better languages ????for it, like python, and all of them are 64 bits, and as I always use OCX that I have the Ctl - many thanks to the contributions of this forum -, it does not seem to me that it is going to be very complex for me to migrate to 64 bits, which for me is really the only reason, because with VB6 I have more than enough, but if Microsoft decides to put problems to the 32-bit programs, that is why I am interested in changing to TwinBasic ...

Many Thanks for your info...!!!