VB 5.0 Setup Error

[roberthpike]

I get an error when trying to install an app I compiled. Basically the error reads "Invalid command line arguments". I had to un-install, unregister a couple of OCX, and then re-install VB 5 just to be able to open it up. It was complaining about License information was out of date for the COMDLG32 and COMCTL OCXs. After performing these couple of steps I was able to open up the project in VB 5 again and execute it fine from within the IDE. Creating the exe performed without any problems too it was only when trying to run the SETUP.exe. Any suggestions would be greatly appreciated. Thanks.

Rob

 

[BobRodes]

Sounds like you're deploying different versions of comdlg32 and comctl than the ones you're using on the development machine. I suggest that you check this first, tell us if this is the case, and also what mechanism you are using to create the installation file(s). If you're using the Package and Deployment wizard (Oh, what do they call that thing in VB5? The Setup Wizard, I think) then it's not surprising that this could occur.

HTH

Bob

 

[roberthpike]

Yes that is essentially what is happening. There is this app I'm working on that was initially created using VB 5. Other applications have been installed on the development machines (some probably written in VB 6) causing the license information to be updated. When trying to open the IDE I got errors (related to COMDLG32) that said license information is out of date. I followed this doc I got off Microsoft's site quite a while ago that talked about un-registering and/or deleting the questionable OCXs off the PC if this license out of date error came up. I un-registered the OCX, deleted the OCX and OCA files, then re-installed VB 5. I was then able to open the application without getting the errors pop up and the program executed fine from within VB 5. I compiled the program into an application and upon attempting to install on the machine (clicking on the SETUP.EXE) I got the error. Any suggestions or do you need more info? Thanks.

 

[BobRodes]

Compiling the program into an application" doesn't create a SETUP.EXE. How do you create the setup file?

Also, if you unregister the older version of the offending OCX files, and reregister the original ones if necessary, does that solve the problem?

Bob

 

[roberthpike]

I understand that the compilation doesn't create a SETUP.EXE, I must have failed to write down that I used the application wizard in creating the application as I've posted this message elsewhere. See the problem of unregistering the old and registering the new is what caused the problem whereby I could not successfully open the project without losing the common dialogs I had on the forms. I said license information out of date. Thats why I set about registering the older version (from VB 5).