Your original question was « What are the pros/cons of doing such a
thing? »; so I answered you about that.
As to your second question - which is more or less irrelevant in my mind if
the answer to the first question is far from beeing positive: to my
(limited) knowledge, such a tool doesn't exist. However, if you search the
internet or ask to a VB6 newsgroup, it's possible that you might find one or
at least, that you might find something that will be able to perform a
partial conversion.
Personally, I seriously doubt that you will find anything capable of doing
that, wheither or not this tool to be cheap and/or capable of doing this job
in less than 2 hours; so I'm afraid that you will have to use your ten
little fingers to do that.
Finally, as to know if the .NET framework will be installed on a target (or
client) machine; don't forget that you will be faced with the same problem
with Java: any Java program require its particular runtime to be installed
and these are far from beeing small.
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
<(E-Mail Removed)> wrote in message
news:0fe591ad-1341-4b63-8174-(E-Mail Removed)...
> Ok, I don't want to convert to VB.NET because I am not sure that
> the .Net framework is going to be installed.
> If it were up to me, then I would choose Java, but it is not up to
> me. I have this ugly wart on my ass and I want it off.
> However that is not my question. I have VB 6 installed on my machine.
> The real question is how to convert from ADP to VB anything.
> Ideally, in under 2 hours using some cheap tool.
|