Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

windows installer and vfp 7

Status
Not open for further replies.

michaelkatz

Programmer
Sep 1, 2002
50
GB
We distribute an applications annually. With the 2005 edition , a customer tried to delete an .exe file with windows explorer. When they next tried to run the application, windows installer tried to install and things went down hill.

We get an error message # 1300, and the line number is non-sensible. The same error now happens for the 2004 and 2003 editions.

Replacing the exe doesn't help.

Any idea what could have happened.

Thanks,
Michael
 
Michael,

Sounds like you need to get the user to re-install the entire app, not just the EXE. Then give them a stern talking-to about the dangers of arbitrarily deleting files.

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)
 
I tried all that. to no avail. They may have aborted the installer. But why should any of this affect prior years. Could the registry have been affected, and can it be cleaned up?

Thanks for any help.
I'm Desperate.

Michael
 
The version of ISE for VFP that came with VFP 7.0 was kind of a "first cut', and there were big improvements in VFP 8.0 and even bigger ones in VFP 9.0.

If your users upgraded the MS Windows Installer (like with XP SP2), that may be the real problem. Consider upgrading to the "real" InstallShield installer, or use a newer version of ISE (and VFP!).

The registry is a big place, and it may be that just the uninstall section may be corrupted. Theoretically, a reinstall shouls have fixed it, but prehaps other changes have made this not possible.

Rick
 
Hi Michael

It appears that some variable is holding a invalid value.. example a very long path.. etc.. May be you can check the path in the specific user computer.

The installation could be looking for a specific file along the path.

Error 1300 points to a missing paranthesis. This could be the effect of a long variable or a macro substitution loosing the end portion of data.

Reinstallation could simply keep adding additional path statements.

:)

____________________________________________
ramani - (Subramanian.G) :)
 
We are using ISE Version 4.01 SP1.

Would changing the Product code and/or Upgrade code help?

Would copying to a new folder make a difference? Once the libraries are registered, why the the registry have to be involved at all.

Thanks.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top