|
Stop autom. updating control versions in VB6 |
Post Reply 
|
| Author | |
Fabian 
Senior Member 
Joined: 22 November 2004 Location: Switzerland Status: Offline Points: 336 |
 Post Options
 Thanks(0)
 Quote Reply
 Topic: Stop autom. updating control versions in VB6Posted: 08 January 2008 at 8:17am |
|
Hi all
Shame on me, but I do not know if and if yes how to to go back to an older version of CJ controls in VB6. Each time I start the VB6 IDE the CJ controls would be updated to the newest version automatically. That is fine, but how can I keep an older version with older CJ controls?
Thanks
|
|
|
Product: Xtreme SuitePro (ActiveX) version 16.2.3
Platform: Windows 7 (32bit) Language: Visual Basic 6.0 / SP6 |
|
 |
|
|
Oleg
Senior Member
Joined: 21 May 2003 Location: United States Status: Offline Points: 11234 |
Post Options
Thanks(0)
Quote Reply
Posted: 08 January 2008 at 3:18pm |
|
Hi,
If you have both old and new versions installed VB will always bug you and you will have always answer "no".
if you don't need new version, uninstall it and manually replace version in vbp and frm files in some text editor.
|
|
|
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS |
|
|
|
|
Fabian
Senior Member
Joined: 22 November 2004 Location: Switzerland Status: Offline Points: 336 |
Post Options
Thanks(0)
Quote Reply
Posted: 09 January 2008 at 1:57am |
|
Hi oleg
Thanks for your fast respose. I have 11.1.3 and 11.2.2 installed but VB6 simply replaces all controls by the newer version SILENTLY???
Any idea?
Thanks
|
|
|
Product: Xtreme SuitePro (ActiveX) version 16.2.3
Platform: Windows 7 (32bit) Language: Visual Basic 6.0 / SP6 |
|
|
|
|
mav46
Groupie 
Joined: 10 November 2006 Location: Italy Status: Offline Points: 63 |
Post Options
Thanks(0)
Quote Reply
Posted: 09 January 2008 at 6:26am |
.. me too in some project, in other ask for the update ? Why ? What is the difference ?
|
|
|
Product: Xtreme SuitePro (ActiveX) 12.1.1
Platform: Win XP (32bit) Language: Visual Basic 6.0 SP5 |
|
|
|
|
joeliner
Senior Member
Joined: 09 June 2006 Status: Offline Points: 273 |
Post Options
Thanks(0)
Quote Reply
Posted: 09 January 2008 at 10:21am |
|
quite a paradox for me, as well. Try this:
Open vb file in text editor. precheck: ensure both old and new ocxs are registered. To make sure you get the correct GUI code for each control, create a new project and add the old ocxs. Then open the project file in a text editor. 1. add the line NoControlUpgrade=1 between  Helpfile="" and Command32=""2. Ensure the Object GUI code pertains to the older version and not the new one. e.g. Object={BD0C1912-66C3-49CC-8B12-7B347BF6C846}#11.2#0; 3. save project and open in VB. P/s: i cant assure anyone twil work but just try. :) |
|
|
|
|
Fabian
Senior Member
Joined: 22 November 2004 Location: Switzerland Status: Offline Points: 336 |
Post Options
Thanks(0)
Quote Reply
Posted: 10 January 2008 at 10:03am |
|
That's exactly what I needed
Thanks a lot!
|
|
|
Product: Xtreme SuitePro (ActiveX) version 16.2.3
Platform: Windows 7 (32bit) Language: Visual Basic 6.0 / SP6 |
|
|
|
|
Post Reply
|
|
Tweet
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
Topic Options
Fabian wrote: