I have to modify a very old VB3 project but I don't have VB3 any longer.
My VB6 system says the source files are in binary format which is not
supported by VB6.
Is there a converter available, or do I have to look for an old VB3
system to convert my files to ASCII?
Thanks -
--
Heinrich
http://www.gartrip.de
mail: new<at>gartrip.de
>Hello,
>
>I have to modify a very old VB3 project but I don't have VB3 any longer.
>My VB6 system says the source files are in binary format which is not
>supported by VB6.
>
>Is there a converter available, or do I have to look for an old VB3
>system to convert my files to ASCII?
>
>Thanks -
Unfortunately the only 'coverter' is VB3 (or 16-bit VB4). The
native/default save was pcode. Saving to an ASCII text file was an
option. If you had the text file you could import them to a VB6
project and get a running program with additional work. But you don't,
and that's that.
You can probably find a VB3 copy with a bit of research (be very
careful downloading from one of those sites) or even buy a legal copy
on eBay. You can also use 16-bit VB4 if you find it. (VB4 comes as two
version in one package a 16-bit and a 32-bit.) VB4 contained utilities
to 'convert' a 16-bit VB3 project to a 32-bit VB4. The 32-bit VB4
would be an easier port to VB6. However, you would still need to do
some additional massage.
Another route, is to seek out one of the decompilers for VB3/4.
However, from a practical stand-point they only work for 16-bit
versions and a ton of additional work would still be necessary to
produce a useable product.
Actually, unless your requirement is to produce a 16-bit executable,
you can probably re-write the application faster than any of the above
options. A lot has changed since VB3, datatypes, the controls, the
data access libraries, and so on. So even if you had the text files
for the VB3 application you would still be looking at a lot of work.
-ralph
I have VB3, VB4 & VB6.
If you ask nicely I might convert it for you.
I still have a VB3 copy on one of my systems. to load your VB3 project
and save it as ASCII should by a piece of cake, IF - and that's a _big_
if - you didn't use any third party controls, which I don't have.
I disagree with ralph. I had some bigger projects in VB3 and I didn't
port to 32 bit VB until VB5. But then it was simple. I remember some
problems with DAO, with the old grid vbx and two major problems with
3rd party controls, especially Apex TrueGrid Pro. Apex didn't provide
an upgrade path, I was forced to rewrite all program parts where I had
used TrueGrid. After they told me so, I decided to not buy their new
OCX and instead use FlexGrid which came free with VB5.
The other problem was an "Invisible Button" that was never ported to
32 bit.
If you can't get hold of a VB3 copy, I'll help you and convert your VB3
files from binary to ASCII.
Look at my email address, just replace the top level domain with de.
Helmut.
Of course, I've still got VB3 installed just like the other guys
who've already offered to convert for you. But the real moral of this
story is "Never Use The Binary Format; Always Save In ASCII".
Cheers
Derek
After I once had a corrupted form file, which was saved in binary
format, I decided to switch to Ascii format. If something went wrong
with a file, you could always recover at least part of your work using
Notepad.
Helmut.