Probem with VB 6 on Win 7 pro 32 and XP pro 32

Hello, I built a small software in vb 6 on win 7 pro 32 bits. I created a installation package using Inno setup. and when I try to test my software in a new fresh copy of win 7 pro 32 bits, I got errors :

Run-time errors, class not registered, looking object CLSID : {...............


I tried to solve that problem myself in registering all DLL that I'm using but problem still going on...

and I also tried to make a installation package using Microsoft deployment (vb 6 tool) that comes within VB 6 but... still nothing


Please, can someone can help me with that project cause I have to return it as soon as possible.




Have a good day

Inno can be difficult, the VB PDW usually works fine.

That said you have not provided enough info to allow for help, no idea what your project uses or maybe be failing to install

please, can you tell me... what kind of information you need to help me, I'm ready to give all you need...

My project is a vb 6 project that use ACCESS database back-end.

if you need other info, please tell me

When you get messages about an object not registered that indicates that you are using 1 or more object in your project that is not part of the windows install. You have not given any hints as to what controls are used in your project nor if you are using any 3rd party controls or dlls so there is not really even a way to guess so far all we know is that you are using VB6, a database and are having a problem with an object. We have no way to know what the object is nor what objects you may be using.

And, Win7 won't let you install certain controls that it has built-in support for...

thanks to help me.

if you want I can send all this small project to you.

please let me know about?



Have a good day

nobody wants to install your EXE (for obvious security reasons)

Yep, and I would not being willign to give my time to scan through the whole project when the poster is not seemingly willing to tell us what is being used. Easier for him/her to type it that us to download and search for it.

Thanks to come to help me "DataMiser and dglienna"

I understand all that you told me and now I'll try to be explicite about the matter.

I developed a Small software in Visual Basic 6 that has a data base built in MS ACCESS.

I linked them from vb instructions / Controls (Objects) like DATA, MSGRID32.ocx, COMDLG32.ocx, Control.ocx, MSCOMCTL.ocx, TABCTL32.ocx, wmp.ocx...

The interface of the software developed in vb 6 will consist to fill
datas in the DATABASE that is built in MS ACCESS.


I compiled it very well without any matter.

I tried to test it in a fresh Win 7 that I only installed the OS wihtout any others programs and there I got this error message

: CLSID:{00000010-0000-0010-8000-00AA006D2EA4} after this

I got another telling : "Object variable or With block variable not set" runtime error" and the software closes down.


This is what's happening to me that I need to solve.

If you need others info, please tell me.


Please, I need your help

Could you post the vbp file and the setup.lst file created by the PDW

This is the Setup.LST file created by PDW


[Bootstrap]
SetupTitle=Installation
SetupText=Copie des fichiers, veuillez patienter.
CabFile=TESTE_PLEASE.CAB
Spawn=Setup1.exe
Uninstal=st6unst.exe
TmpDir=msftqws.pdw
Cabs=1

[Bootstrap Files]
File1=@VB6STKIT.DLL,$(WinSysPathSysFile),,,3/26/99 3:00:00 AM,101888,6.0.84.50
File2=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,6/1/98 12:00:00 AM,22288,4.71.1460.1
File3=@VB6FR.DLL,$(WinSysPath),,$(Shared),7/13/98 12:00:00 AM,119568,5.0.81.69
File4=@stdole2.tlb,$(WinSysPathSysFile),$(TLBRegister),,7/14/09 12:43:53 AM,16896,6.1.7600.16385
File5=@asycfilt.dll,$(WinSysPathSysFile),,,3/5/10 8:42:42 AM,67584,6.1.7600.16544
File6=@olepro32.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,7/14/09 2:16:12 AM,90112,6.1.7600.16385
File7=@oleaut32.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,8/27/11 5:43:07
AM,571904,6.1.7600.16872
File8=@msvbvm60.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,7/14/09 2:15:50 AM,1386496,6.0.98.15

[IconGroups]
Group0=Projet1
PrivateGroup0=Faux
Parent0=$(Programs)

[Projet1]
Icon1="TESTE_PLEASE.exe"
Title1=Projet1
StartIn1=$(AppPath)

[Setup]
Title=Setup_EJCSK
DefaultDir=$(ProgramFiles)\Projet1
AppExe=TESTE_PLEASE.exe
AppToUninstall=TESTE_PLEASE.exe

[Setup1 Files]
File1=@BD_FIDELES.mdb,$(AppPath),,$(Shared),2/25/13 4:06:24 PM,395264,0.0.0.0
File2=@DBGRID32.OCX,$(WinSysPath),$(DLLSelfRegister),$(Shared),6/24/98 10:55:26 AM,525352,5.1.81.4
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
File5=@TABCTL32.OCX,$(WinSysPath),$(DLLSelfRegister),$(Shared),12/5/00 11:00:00
PM,209608,6.0.90.43
File6=@MSCMCFR.DLL,$(WinSysPath),,$(Shared),7/13/98 12:00:00 AM,141312,6.0.81.63
File7=@MSCOMCTL.OCX,$(WinSysPath),$(DLLSelfRegister),$(Shared),12/20/02 2:02:44 PM,1077336,6.1.95.45
File8=@CMDLGFR.DLL,$(WinSysPath),,$(Shared),7/13/98 12:00:00 AM,32768,6.0.81.63
File9=@comdlg32.ocx,$(WinSysPath),$(DLLSelfRegister),$(Shared),5/23/00 12:58:00 AM,140488,6.0.84.18
File10=@wmp.dll,$(AppPath),,$(Shared),9/1/10 5:29:28 AM,11406848,12.0.7600.16667
File11=@TESTE_PLEASE.exe,$(AppPath),,$(Shared),2/26/13 1:48:09 PM,671744,1.0.0.0

; Il est possible de supprimer les lignes suivantes afin de libérer
; de l'espace pour personnaliser ce fichier sur une disquette d'installation
; complète.
;
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
;
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
;
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
;
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


=== END ===

MSGRID32.ocx is probably already there. Did you try just running the exe without running the setup? You can kind of manually copy files and data to the right location, and then run an installation that just creates the exe. That will allow the program to either start, or tell you which file it might be looking for. (Also, in system logs)

Thanks I'll try and I'll back to you.

Look at the VBP file with notepad you should be able to match the CLSID with the object causing the problem

example snippet from a vbp

Quote:

---

Type=Exe
Form=frmMainTest.frm
Reference=*\G{00020430-0000-0000-C000-000000000046}#2.0#0#..\..\..\..\WINDOWS\system32\stdole2.tlb#OLE Automation
Module=modreg2005; ..\..\Shared\CommonFiles\modreg2005.bas

---

Example from another VBP

Quote:

---

Object={248DD890-BB45-11CF-9ABC-0080C7E7B78D}#1.0#0; MSWINSCK.OCX
Object={6B7E6392-850A-101B-AFC0-4210102A8DA7}#1.3#0; comctl32.ocx

---

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

Quote:

---

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?

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

Thanks, I'll do and I'll be back.