It probably is a simple solution but I just can't find
it. Hope you can help.
Regards from Downunder
Alan Aston
"Alan Aston" <anon...@discussions.microsoft.com> wrote in message
news:02e701c3a893$455604f0$a401...@phx.gbl...
I ended up using "DEPENDS.EXE" to track down offending DLL's to be sure I
included them all in my install....
What version of VFP 8 do you have? If you compiled the exe under VFP 8.0
SP1 but gave them the VFP8r.dll and VFP8renu.dll for VFP 8.0, then you
could see this problem. Go to the development machine and type ?VERSION()
in the Command window and then check the version of the runtime files using
Windows Explorer. Are they the same?
Also, what operating system are you using? VFP 8.0 is not designed to run
on Windows 95 systems.
I hope this helps.
This posting is provided "AS IS" with no warranties, and confers no rights.
Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell
*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518
Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retires Sept. 30th, 2003