Hi all,
I'm a new member here. I need your help for a problem with VB6 program. I have program that has only one form that capture an input and opens the right file if it is found in the directory specified. I can run that program in my pc. So, then i created setup and tried to install in my clients pc but I got an error. I installed vb in that pc and run the program, the error message was Run-Time Error 430:Class does not support Automation or does not support expected interface.
Please desperately i need help on this.
Regards/shena
Aloha Shena,
You definitely are not deploying all that is needed for your app to run.
1 - What installer did you use to create your installation?
2 - what references and components are you using in your application?
3 - What files are you deploying?
Hi,
Thanks for your reply.
The file that I try to open is a printing software's file (.btw) called Bartender Software. I added only two references in VB6, Bartender 7.74 and HHActiveX.dll. The rest of the files were included in support folder when i used package and deployment wizard. But, when i run the setup at client's pc but this is the error that I've got:
Setup cannot continue because some system files are out of date on your system. Click OK if you would like setup to update these files now. You will need to restart Windows before you can run setup again. Click Cancel to exit setup without updating system files.
I have tried to restart and reinstalled, but it prompted me the same error message again and again.
Yes, that is an inherent problem with PDW. It hasn't been updated since 1998, so it is really out of touch with installation in the present day. You can still use it if you like but you will need to do some tweaking to get it to work. First you will need to use the universal VB Runtime files (they can be found at https://randemsystems.com/freeware.html (https://randemsystems.com/freeware.html)) and you should read https://randemsystems.support/innoscript-general-questions-report-bugs-problems-etc/installation-problems/ (https://randemsystems.support/innoscript-general-questions-report-bugs-problems-etc/installation-problems/) to better help.
Or you can use Inno Setup (http://jrsoftware.org/isdl.php (http://jrsoftware.org/isdl.php)) along with InnoScript (https://randemsystems.com/innoscript// (https://randemsystems.com/innoscript//)) and be kept up-to-date. This will make creating an Installer simpler.
If you zip and post your project .vbp, .exe and HHActiveX.dll files (3 files) I can take a look to see what I can see.
Hi,
I have uploaded my project. It always highlights this part: btApp.Visible = True when i click debug in client pc.
Please re-upload as a .zip file.
Ok, reuploaded.
Try this...
Hi, I've got the same error message:
Run-Time Error 430:Class does not support Automation or does not support expected interface.
Ok, I will look at your code.
This should work for you. BTW you are hard coding a path. A BIG NO_NO!!!
Installation
ESDLabel0100000Release.zip (https://randemsystems.support/index.php?topic=1.0) (5055.2 k)
So, how is your progress?
Hi, thanks for the advice on hard coding a path. But, though the file exist in the directory, but program prompted File doesn't exist. (the 1st attacment-form code) Whereas, for second attachment I've got the same error message. But, it runs perfectly in my pc, not in my client's pc (Windows xp service pack 2). The App.Path refering C:Documents and SettingsshenaDesktop, is it by default? Because I'll always keep the files in C:ESDLabel.
App.Path is returning where the program was invoked from. You really should rethink about C:\ESDLabel location. What if the clients computers system drive is d: or e: or any other drive? What if C: is the CD? Your application will fail miserably.
For app.path to have the location you state you would have had to COPY the exe to the desktop and not have a shortcut on the desktop.
OK, understood. I have already changed the path definition method. I'm not sure whether the bartender software is creating the problem or project component/reference. Hence, I will uninstall and then reinstall the software at client's pc to see what happen. Hope it works.