The reason i need Active X is because i plan to Make a visual basic for applications compiler
So I could use visual basic for applications macros after Microsoft kills them
Probably in 2014 Microsoft will make a new version of office without VBA6
The point of my app is for vba developers to produce an exe from there projects
similar tho those produced with vb5/6
I would want to add multi platform support but Vba is to Dependant on Active X for controls
If they were converted to multi platform source files
some would work others would simply break
i want at least 50% to work
My vba compiler should work something like this
VBA FRM + MY APP(VBA compiler)= C++ files
C++ files + C++ Compiler > EXE
It should run on any platform office 2000 and VB5 ran on
And for multi platform i could use these
http://www.winehq.org/http://en.wikipedia.org/wiki/Gambas (not C++)
It probably would be windows only but i could add the option to create C++ or Gambas source code That may be compiled under non windows
this may only work for vba apps that only used fm20.dll
or may require recoding of VBA apps that used others but that is what the compiler is to avoid
I wanted to use C++ because i have seen this on wikipedia and other sites
"The Visual Basic compiler is shared with other Visual Studio languages (C, C++)"
Also C++ is more powerful than basic
so there may be a way to load an Active X (OCX) with code
with code using the OLE dll files in code
For the first version it will be windows only and simply do a few things
in some later releases when some simple lines of code work i would add some multi platform support
To do list
1 VBA gui converter
2 VBA Code converter
3 VB5/6 support
4 REACT OS support
5 Multi platform support