Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Errors trying to view forms in Design Mode

Status
Not open for further replies.

matrixtech

Programmer
Dec 3, 2001
12
0
0
US
Hello,

I have a project that contains about 7 forms. It was created with VB
enterprise and I can view the code behind all of the forms through the
project explorer, but if I try to view the actual form using the project
explorer, I get an error that says there were errors during the loading of
the form. I was able to view the forms about 2 weeks ago. This is what was
written to the error log:

Line 103: Property in txtRoyaltyRate could not be loaded.
Line 547: Property in txtcost could not be loaded.
Line 591: Property in txtprce could not be loaded.
Line 615: Property in txtprics could not be loaded.
Line 633: Property in txtcosts could not be loaded.
Line 724: Property in txtValue could not be loaded.
Line 1289: Property in txtRoyaltyTot could not be loaded.
Line 1307: Property in Text2 could not be loaded.
Line 1325: Property in Text1 could not be loaded.
Line 1343: Property in txtValAdded could not be loaded.

I tried reinstalling visual basic to no avail. I also transferred the files
to another computer and I was able to view the forms just fine.

Anyone have any ideas?

Appreciate it,

Geoff





 
Geoff,

This can sometimes happen if you have installed a visual basic application on your development machine. What happens is that the activeX controls lose their development license and can't be used in VB anymore. Also this can happen if a rogue application overwrites your comctl32.dll with an older version. In this case, the GUID reference in your form will not match with the correct version of the comctl32.dll file.

I think I have also seen this happen when you have two development environments on different service packs.

Check to make sure all your VB machines are on the same service pack (this is VERY important!).

Try copying the comctl32.dll file from the "working" box to the not working one and regsvr32 it.

There is also a MSDN article about this problem with the development license thing etc.. but I couldn't find it, sorry! Are you using vb5?

-recurse
 
Hey Recurse,

I was unable to unregister the comctl32.dll on the "non-working" box using regsvr32.

This is the error I got.

Comctl32.dll was loaded but the DllUnregisterServer entry point was not found. DllUnregisterServer may not be exported, or a Corrupt version of Comctl32.dll may be in memory. Consider using PView to detect and remove it.

Any ideas?

Thanks
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top