1 Attachment(s)
VB Project Opening Problem
Dear All,
I am got a VB 6.0 project through internet which is a very nice one.
it is having forms and class modules when i am trying to open the project main file (that file is project.vbp file)
The forms and class modules are not opening along with project.vbp
when i am trying to open the individual forms some of them are loading some of them are showing errors like
"error loading the file " and they generating .log files with form name ,
and some of the showing
"Out of Memory" error.
HTML Code:
[IMG]C:\Documents and Settings\Administrator\Desktop\error1.jpg[/IMG]
Re: VB Project Opening Problem
Did you read the log file? It usually tells you exactly what happend - control could not be loaded or something like that.
Re: VB Project Opening Problem
most likely u reinstalled windows ,and vb6 cant find the path to the file its trying to load
Re: VB Project Opening Problem
If it was free, you could post the link, and one of us can give it a run
Re: VB Project Opening Problem
This thread is nearly 3 years old OP has probably resolved the problem.
Re: VB Project Opening Problem
Quote:
Originally Posted by
Doogle
This thread is nearly 3 years old OP has probably resolved the problem.
LOL... how do they find these threads? It happens all the time... :) :confused: :rolleyes:
Re: VB Project Opening Problem
Quote:
Originally Posted by
Doogle
This thread is nearly 3 years old OP has probably resolved the problem.
They have to get up early in the morning to fool me.
OOPs
Re: VB Project Opening Problem
I solved this problem, though I'm not sure how it fixed it. Below are the differences between the Older version of the Project and the most recent version.I suspect that the New Project had : Object={648A5603-2C6E-101B-82B6-000000000014}#1.1#0; MSCOMM32.OCX
The Older Project had: Object={86CF1D34-0C5F-11D2-A9FC-0000F8754DA1}#2.0#0; MSCOMCT2.OCX and it worked
Also, there were Forms Files Missing. These were new in the most recent project and are not critical to application. I will need to add them at some point.
The rest of the differences are minor and I don't know if they contributed to the problem.
New Project - Didn't work Old Project Version - Did Work
Bad Reference=*\G{54AF9343-1923-11D3-9CA4-00C04F72C514}#2.32#0#..\..\WINDOWS\system32\odbcconf.dll#Microsoft Data Access Components Installed Version No Reference - Not Used
Bad Reference=*\G{00000600-0000-0010-8000-00AA006D2EA4}#2.8#0#..\..\Program Files\Common Files\System\ado\msADOX.dll#Microsoft ADO Ext. 2.8 for DDL and Security No Reference - Not Used
Bad Reference=*\G{905F5470-EB94-11D1-AB0E-00AA00BDD685}#1.0#0#..\..\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\PDADDIN.DLL#Package and Deployment Wizard No Reference - Might Be one reason why this Project Failed?
Bad Object={2398E321-5C6E-11D1-8C65-0060081841DE}#1.0#0; Vtext.dll No Reference - Not Used
Bad Object={582C2183-4016-11D1-8C55-0060081841DE}#1.0#0; Vdict.dll No Reference - Not Used
Bad Object={831FDD16-0C5C-11D2-A9FC-0000F8754DA1}#2.0#0; MSCOMCTL.OCX Not needed - Removed
Bad Module=mCommonDialog; mCommonDialog.bas New Module - Not needed. Added in New Project
Bad Module=frmAnalyzeEmailFields; Analyze_Email Fields.bas New Form - Not needed. Added in New Project
Bad Form=SetupFixDialog.frm New Form - Not needed. Added in New Project
Bad CodeViewDebugInfo=-1 CodeViewDebugInfo=0
Thank you everyone who responded!
genepester