eeevbeee
asked on
Read/Write Excel - DLL ??
I have a vb6 program that reads and writes an Excel Worksheet. Now this works fine on the developement machine, but when I made a project and installed onto another PC there I get an Error. It seems to b missing a neccessary DLL.
What DLL do I need to include for this to work??
What DLL do I need to include for this to work??
what is the exact Error what does it say.. or is it just a number....
Have you set a reference to the Excel object library for your version of Excel?
Wes
Wes
There are several Dlls required by VB6 - here's a the main ones:
Uses1=MSVBVM60.DLL
Uses2=OLEAUT32.DLL
Uses3=olepro32.dll
Uses4=ASYCFILT.DLL
Uses5=STDOLE2.TLB
Uses6=COMCAT.DLL
If you want you could copy them accross, but normally you would use something like The Package and Deployment Wizard - this builds an installation package which the user will run in order to install all neccesary components on to their machine.
Uses1=MSVBVM60.DLL
Uses2=OLEAUT32.DLL
Uses3=olepro32.dll
Uses4=ASYCFILT.DLL
Uses5=STDOLE2.TLB
Uses6=COMCAT.DLL
If you want you could copy them accross, but normally you would use something like The Package and Deployment Wizard - this builds an installation package which the user will run in order to install all neccesary components on to their machine.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you used any scripting make sure the Package & Deployment Wizard included the scrrun.dll
As Lewy said, you ABSOLUTELY need Excel to be installed on the user's PC.
The Package & Deployment Wizard (or InstallShield or Wise Installation or any other) won't distribute Excel (Word or Visio or Explorer or Project or ... any applications used by OLE Automation) because you don't have right to distribute it.
The Package & Deployment Wizard (or InstallShield or Wise Installation or any other) won't distribute Excel (Word or Visio or Explorer or Project or ... any applications used by OLE Automation) because you don't have right to distribute it.
ASKER
OK
Here are answers, comments...
Development Machine is win98, target machine is WinNT
All the compenents that NikWhitfield mentioned are there
scrrun.dll is in WinNT\system32 but not in the package
I did use the VB setup package to create the setup
>>Have you set a reference to the Excel object library for your version of Excel?
probably not. What am I to do?
Error message:
409
activex component can't create object
Here are answers, comments...
Development Machine is win98, target machine is WinNT
All the compenents that NikWhitfield mentioned are there
scrrun.dll is in WinNT\system32 but not in the package
I did use the VB setup package to create the setup
>>Have you set a reference to the Excel object library for your version of Excel?
probably not. What am I to do?
Error message:
409
activex component can't create object
ASKER
one more thing
the target machine does NOT have Excel installed.
the target machine does NOT have Excel installed.
It have too! You have no other choices. PDW CAN'T distribute Excel.
ASKER
YES!!!
It needed Excel. I figured that this would be handled by some of VB's .dlls.
But to whome do I give the points?
It needed Excel. I figured that this would be handled by some of VB's .dlls.
But to whome do I give the points?
>It needed Excel. I figured that this would be handled by some of VB's .dlls.
VB don't handle them 'cause of the distribution rights.
>But to whome do I give the points?
It seems that you have the choice between Lewy and me.
VB don't handle them 'cause of the distribution rights.
>But to whome do I give the points?
It seems that you have the choice between Lewy and me.
ASKER
emoreau
i am taking Lewy's as it was first, and and I am posting another fantom q for u to answer so that I can give you points too. thanks
i am taking Lewy's as it was first, and and I am posting another fantom q for u to answer so that I can give you points too. thanks