Packaging Problem?

Howdy all,

I was getting the following error:
429 - Activex Component can't create object has occured in the application...

When I simply copied the exe to another computer, then I tried the packaging and deployment wizard but I'm having the same error even after doing an install. Is anyone familar with this error?

The application is a one form deal that examines a text file and writes information to several output files (.csv excel file, sql table and a couple of reporting text files) It was working perfectly until I added a filesystemobject so it could read the source file (source file may or may not have a linefeed only or linefeed/carriage return combination) correctly. I've come to the conclusion that I've messed something up in the package and deployment wizard because it works fine on my development pc with the FSO code added.

Any help would be greatly appreciated.

rp

did you ever edit the files the package/deploy wizard uses (and i mean the actual forms the setup program uses, i.e., did you ever rebuild the setup wizard or have you only always just used it through the p/d wizard)?

just trying to eliminate what comes to mind. i've had little problem with the p/d wizard... SO FAR.

also what flavors of windows are the two machines on? if one is win98 or higher and the other is win95 then getting it to work may take some more profound effort than just running the p/d wizard.

----------
"Assembly of Japanese bicycle require great peace of mind."

I haven't modified the P&D wizard in any way and both machines are running the same software (MS office 98, win98). I just don't get it. Both machines were running the application without needing an install and all I changed was the way the source file is read, changing it from a

line input #filenumber, sline
to
sline = filename.readline

type arrangement.

rp

First, take a look at your project's ocx. This error message shows that some ocx or dll was not registerly properly or is corrupted.

if you want to hit the stars,shoot to the sky.

Rod - are you sure you mean look at the OCX? they are compiled ActiveX controls... you can't look at them. I think you mean look in the *.log file thats generated when a VB project fails to load for whatever reason. images/icons/wink.gif

Chief



"How are we to learn, if those that know will not teach... ?" - Me.

I copied this line out of an old package Setup.lst file. If you don't have
a similar line (that references scrrun.dll,) then you need to redo your
package, including that dll.
File11=@SCRRUN.DLL,$(WinSysPath),$(DLLSelfRegister),$(Shared),1/15/99 12:00:00 AM,151824,5.0.0.3715

I think therefore I am... sometimes right. images/icons/wink.gif

Thinker I owe you again. Works perfectly, misread your original post but now I understand. Could you tell me how you knew that driver was the problem? Additionally could you tell me how you track down the drivers the P&D does not automatically list if your program installation has problems?

Thanks
rp

<P ID="edit"><FONT class="small"><EM>Edited by rpeare on 10/03/01 11:51 AM.</EM></FONT></P>