Creating 16 bit vb4.0 app under '95 will not run under win 3.1
Recompiled the program under Win 3.1?? As in, "just install VB4-16 on
your Win 3.1 machine" ? Or as in, "just re-create your app under
VB 3.0" ? Either way, some problems just don't go away! Take mine,
for example:
image1.picture=loadpicture(combo1.text)
This crashes everything but VB4 32-bit. I wrote it on VB3/WFW3.11, and it ran.
I saved it as VB4-16 bit under NT and it got wonky. I moved it back to
VB3/WFW3.11 and it still won't run. I moved it to Win '95 VB4-16 and
it is no go. I moved it to VB4 32-bit/Win 95 and it runs like a dream.
I think I accidently compiled it under VB4 32-bit at one point (instead of
16-bit, and I may even have saved it as 32-bit code, if there is such a thing
apart from code that makes 32-bit calls....) But it definitely wasn't
healed by moving to Win 3.1x/VB3!
Regards.
Ned Bedinger
Quote:
>*****
>I ran across an interesting situation... I created a program using
>vb4.0 in windows '95. I went to run the program on a different computer
>running windows 3.1 and guess what... I got an error "OUT OF MEMORY".
>I tried another windows 3.1 machine, and another ... always with the
>same error. I re-compiled the program underneath win 3.1 and it went
>away...
>Go figure...
>*****
>Hi,
> I have a similar (not sure about that ?) problem with VB3PRO
>written on Win95. It just won't work on Win 3.1. I had a few 'Out of
>memory' messages and some errors that just don't show up on Win95. Since
>finding a Win 3.1 machine that runs VB3 will not be very easy for me, I
>would like to ask you if your Win 3.1 compiled program runs on Win 95
>(which is essential for me).
> Thanks for posting this observation, you might have found the
>solution (and how simple that one was) to a problem nobody could solve.
> Sylvain (AlwaysTheNewbieOne)
