Thanks
OlimilO for the clarification and sorry about the terminology.
Iam working on a test program that reads DLL libraries (Classes, events, procedures/functions, and enumeration constants) for example the ADODB library and generates skeleton classes and modules that can latter (may)be imported into Jabaco. The skeleton procedure or sub could then be written to provide the same functionality as its VB counter part ...
Having to use the # between the namespace and class would still make it difficult to import code from vb referencing the ADODB library ... but maybe easier than to rewriting the code ???
Does anyone think this could be of help as personally even though I really like the Jabaco concept its still very difficult to get a mid to large size application to port without major changes. A lot of these changes will require a decent amount of Java programming which if acquired makes me wonder why not port directly to Java ...
Thanks again for your help