I was going to reply to an earlier thread about this subject, but I can't seem to locate the original thread.
It just started happening the other day that I am no longer able to manually resize any VB controls in my projects. I've had my new machine for a while now and had used the VB6 IDE with no problems.
Now, I can only resize controls using the SHIFT + ARROW method. And no, the 'lock controls' option isn't set on the form.
No, the files aren't marked as 'read only'.... It was mentioned in the thread that a reinstall didn't solve the problem, but I might go ahead and try that option anyway.
No, the files aren't marked as 'read only'.... It was mentioned in the thread that a reinstall didn't solve the problem, but I might go ahead and try that option anyway.
I would if I were in your shoes. Ensure you elevate permissions if installing on Vista/Win7, definitely run as administrator or turn UAC off. You might want to give a quick forum search regarding VB6 installation and Vista or Win7.
Insomnia is just a byproduct of, "It can't be done"
Merri or Marty, you removed your reply. Didn't catch who exactly it was -- ghoster!
I think it was a great troubleshooting idea: Lock the controls, then unlock the controls to see if it is resolved (i.e, toggle the lock function). Maybe save changes between the toggling. But if this problem applies to all new projects too, then I doubt it will solve anything.
Last edited by LaVolpe; Nov 6th, 2010 at 12:19 PM.
Insomnia is just a byproduct of, "It can't be done"
Merri, you removed your reply. I think it was a great troubleshooting idea: Lock the controls, then unlock the controls to see if it is resolved (i.e, toggle the lock function). Maybe save changes between the toggling.
You meant me I assume and I'm only Merri some of the time Anyhow I suggested that it might be the Lock Controls Toggle but then I reread the original post and saw that the poster said that that wasn't it.
You meant me I assume and I'm only Merri some of the time Anyhow I suggested that it might be the Lock Controls Toggle but then I reread the original post and saw that the poster said that that wasn't it.
Hence toggling from on to off is a good idea; whether it works or not is another question. The referenced thread in reply #2 didn't attempt that idea. And yes I mean't you. All you 2-syllable guys whose handles start with 'M' look the same to me
Insomnia is just a byproduct of, "It can't be done"
Several of us at the company I work at have the same issue. The common "Thread" with these systems is that we have both Visual Basic 6 (SP6) loaded along with Visual Studio 2010. The problems started occuring right after loading Visual Stuido 2010. I have not tracked down the problem yet, but this might help eveyone on this post find a quick solution. I am betting it is something in the Windows Registry, but I am not 100% sure yet. Please let me know if anyone finds out what the issue is between Visual Stuido 2010 & Microsoft Visual Studio 6.0(SP6). Also, all of our systems are Windows XP SP3 with all updates applied.
One other thought.... We also have Visual Studio 2008 loaded so we can convert the code from VB6 to the .NET Framework. Unfortunately, Microsoft dropped the conversion from VB6 in later versions of Microsoft Visual Studio and you must load 2008 to convert VB6 -> Visual Studio 2010. The problems did not start until Visual Studio 2010 was loaded....
I verified that it is, indeed, Verdasys Digital Guardian causing the issue. I uninstalled the application and the sizing returned to the way it should. Going forward this will not be an issue because I can just uninstall it on any machines I'm coding VB Studio 6 (C,VB,ect it's all IDE). This issue is now resolved.
Thanks
PS: Installing breaks, uninstalling fixes. It seems that tcurrier also confirmed that he has Digital Guardian Agent (Verdasys) installed and continues to have the issue. My suggestion would be to get the uninstall key or force uninstall it without and continue to code up using VB6.
You do realize that this thread is 2.5 years old, right?
Yes, this was referenced in the link posted. This is what I came across when doing a search and decided, like a good citizen, I'd post up the resolution for future patrons who may stumble on the same problem.
Although this thread is 7 years old, I, too, had the very same problem this morning (11 August 2017) with resizing the form at design time (VB6 SP6), and these comments may help someone who is also searching for a fix, since I believe there are still a great many VB6 enthusiasts out there.
What I did to fix it was add a new form to the same project, then copy all the controls AND the code from the "busted" form to the new form. Then I saved the whole lot in a temporary folder. Then I reloaded the .vbp from the temporary folder and removed the "busted" form. The only other thing I needed to do was set the Startup form and rename the new form from frmTemp to frmMain. Bingo! The problem has gone and I can resize the form again.
Note that when I first saw this problem I noticed that the min/max icon in the caption bar was set to max, even though the form's Windowstate property was 0 (vbNormal). Also, I could right click on the caption bar and the menu included Restore (not greyed out). By clicking on Restore the min/max icon changed to vbNormal and the form became resizable. Even after saving the project again, then reloading it, the problem was fixed.
I never experienced this problem before. The code example which I'm modifying came from a CD-ROM in the back of a computer book*. It's possible that the original code (on the CD) was saved in VB5 format. Otherwise I have no idea why this happens sometimes.
* "Visual Basic 5 Web Development by Scott Jarol (1997)
If I was curious, I sure would have save the original non-working files and then do file compares to see what the difference in the files were. Perhaps even move the files one by one back to see if the problem would reappear when a particular file was restored.
Well, I played around with several options for the MinButton, MaxButton, WindowState, & BorderStyle proproperties (often using an ANSI editor to change them) and couldn't make it fail.
I also downloaded the files from posts #13 & #14, and that also worked fine (and that was suppose to illustrate the problem). So, unless someone can illustrate the problem, I'm going to assume this is a non-issue.
Best,
Elroy
Any software I post in these forums written by me is provided "AS IS" without warranty of any kind, expressed or implied, and permission is hereby granted, free of charge and without restriction, to any person obtaining a copy. To all, peace and happiness.
Re: If I was curious, I sure would have save the original non-working files and then do file compares to see what the difference in the files were. Perhaps even move the files one by one back to see if the problem would reappear when a particular file was restored.
This could still be achieved, because the original code is on the computer book's CD-ROM.
Last edited by LittleTyke; Aug 12th, 2017 at 03:35 AM.
Reason: Forgot something.
I believe the issues and solution were described in post #29 of the link provided in post #23 of this thread.
Spoo
In that post #29 the author claimed it was something called Verdasys Digital Guardian that was causing it. But I have never heard (until now) of Verdasys Digital Guardian and never installed it. I've just checked my Add or Remove Programs list and the list does not contain Verdasys Digital Guardian or anything similar. Also, note that my problem only occurred with this one .frm from a very small demo project on a computer book's CD-ROM.
On my PC I have over 3,000 VB projects and I did a random check of several and none of them exhibited the problem. Also, the problem was only confined to the form, not the controls upon it. I could resize the controls, just not the form.