VB5 OCX version problem 
Author Message
 VB5 OCX version problem


I'm working on a VB5 project which utilize some OCX (common dialog, SStab,
etc). I found that if I upgrade something (os 95->98, VB5->VB6, etc), some
OCX will be upgraded to a new version.
The wrost thing is that when I open my VB5 project now, some OCX won't be
loaded. For simple control like common dialog, I can drag a new one. For
some OCX like SSTab, where I have many tabs and properties set, I need to
work hard to rebuild it!

Someone teach me to edit the .frm / .frx file, but I wonder why we need to
do such thing! Are there any better methods to prevent it??


Mon, 31 Dec 2001 03:00:00 GMT  
 [ 1 post ] 

 Relevant Pages 

1. need VB5 help with Custom OCX version problem

2. Latest versions of ocx and dlls for VB5

3. vb5 vs comctl32.ocx versions

4. vb5 comctl32.dep for comctl32.ocx (version 5.00.3828)

5. Access97: Version problems with comctl32.ocx

6. comctl32.ocx (Problems with Version 1.1)

7. Comctl32.ocx:version problems

8. Version Problems? mscomctl.ocx

9. COMCTL32.ocx version problem

10. MSACAL70.OCX / MSCAL.OCX: NLS versions?

11. VB5 performance problems with True DBGrid (any version)

12. VB5.0 Academic Version and Standard version: Difference?


Powered by phpBB® Forum Software