-
April 3rd, 2013, 01:31 PM
#16
Re: Probem with VB 6 on Win 7 pro 32 and XP pro 32
I did a quick search of my code folders for that ID and found no matches so I would think this rules out the commonly used objects.
I would say it is one of these
File3=@Control.ocx,$(WinSysPath),$(DLLSelfRegister),$(Shared),2/8/04 8:32:02 PM,499712,1.0.0.0
File4=@TABCTFR.DLL,$(WinSysPath),,$(Shared),7/13/98 12:00:00 AM,21504,6.0.81.63
File6=@MSCMCFR.DLL,$(WinSysPath),,$(Shared),7/13/98 12:00:00 AM,141312,6.0.81.63
File8=@CMDLGFR.DLL,$(WinSysPath),,$(Shared),7/13/98 12:00:00 AM,32768,6.0.81.63
File10=@wmp.dll,$(AppPath),,$(Shared),9/1/10 5:29:28 AM,11406848,12.0.7600.16667
That first one is unknown, is it possible that it requires an additional file that is not being included in your setup?
Always use [code][/code] tags when posting code.
-
April 4th, 2013, 06:39 AM
#17
Re: Probem with VB 6 on Win 7 pro 32 and XP pro 32
Control.ocx object is just for changing vb 6 command button appearence, it gives them a Win XP button appearence.
I took this object "control.ocx" from a source-code project that I downloaded from www.codes-sources.com, and I found better to insert it in my project too.
Yes, I'll compile the project without "control.ocx" and I'll be back to you.
Thanks
-
April 4th, 2013, 06:49 AM
#18
Re: Probem with VB 6 on Win 7 pro 32 and XP pro 32
Thanks, I'll do and I'll be back.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|