Quote Originally Posted by yereverluvinuncleber View Post
Instead of VisualBasic for Applications or its equivalent TwinBasic for Applications, just use TwinBasic 4 Application

The four uses of TB:

1. VB6 replacement
2. VBScript replacement
3. VBA replacement
4. and the fourth being... hmmm a successor to VB.NET... just grabbing things from the air, JSCRIPT alternative, I don't know.

or plain and simple: a TwinBasic 64 Application, it sounds almost the same and it has 'four' in the name.
My MAIN reason for looking into twinBasic as a replacement for VB6 is to continue development and support for my company's VB6 products. Sadly, none of them can be imported successfully into twinBasic. I am able to import only small utilities.

I'm sure that Wayne is hard at work on new features but for my use case, this is not a viable VB6 replacement until it can handle my large, complex apps. I think that more focus needs to be spent on that, if you want to draw more to twinBasic. I know I would seriously consider switching over 100% right now, if my apps worked in tB.