Avoiding load of 32-bit custom control using 16-bit Visual Basic 4.0 
Author Message
 Avoiding load of 32-bit custom control using 16-bit Visual Basic 4.0

Dear VB guru,

I'd like to avoid having two different versions (32-bit and 16-bit) of the
same form.  I'm using the comctl32.ocx's ProgressBar control in my 32-bit
VB4 program.  There is no 16-bit version.  Unfortunately, I still must
support 16-bit users.

I haven't found a way to get VB4 to avoid trying to load the control when
running in 16-bit mode.  The #if win32 doesn't work (causes a failure to
load the form) in the "begin end" blocks in a ".frm" file.

One idea is to load the control "dynamically" at run time when the form is
loaded but I don't know if this is possible.

Thanks for your help.

George



Sat, 30 Oct 1999 03:00:00 GMT  
 
 [ 1 post ] 

 Relevant Pages 

1. Multimedia control for Visual Basic (16 bit or 32 bit)

2. shared variables between Visual Basic (16 bit) and Visual C++ (32-bit)

3. VB 4.0 (16-Bit)/Crystal Reports 3.0.1.32 (16-Bit) Print Preview Maximize Window

4. corruption of 16 bit db when used by both 16 and 32 bit apps

5. VB 4.0 16 bit or 32 bit Escape Key

6. VB 4.0 conversion from 32 bit to 16 bit

7. VB 4.0: 16 bit vs 32 bit

8. 16 bit API calls in VB 3 supported in 32 bit VB 4.0

9. VB 4.0 (16 bit vs 32 bit)

10. CARDS.DLL 16 Bit doesn't work on VB 4.0 32 Bit

11. CARDS.DLL 16 Bit doesn't work on VB 4.0 32 Bit

 

 
Powered by phpBB® Forum Software