Here I am again, with almost the same problem, this time with VFP 7.0.

I'm trying to run an executable created in VFP 7.0 on a server that uses

Windows 2000, and I'm getting the library error ("Cannot locate the

Microsoft Visual FoxPro support library.") I've added vfp6r.dll,

vfp6renu.dll files to the C:\WINDOWS\SYSTEM32\ and C:\WINDOWS\SYSTEM

directories on the server (just in case it should be one or the other,

so you have you first clue that I don't know what I'm doing, I suppose).

No go.

I also created a directory containing the .DLL files and my executable,

on the theory that Windows 2000 wanted everything in the same place. No

go. The new directory has been added to the PATH statement.

I'm not using InstallShield, but rather creating the executable from the

FoxPro project, which has worked for me until this problem arose. How

can I include the runtime files when the executable is created, so that

it will run on Windows 2000?

Thanks,

Catherine Hines

I believe the message you are getting is correct.

The EXE is built with VFP 7, you have copied the VFP 6 DLL's

have a quick at this page:

http://fox.wikis.com/wc.dll?Wiki~VFP7RuntimeFiles

Tracy Pearson

PowerChurch Software

828-665-1818

> -----Original Message-----

> From: Hines, Catherine

> Sent: Tuesday, January 24, 2006 11:22 AM

> Subject: FW: "Cannot locate the Microsoft Visual FoxPro

> Support Library" VFP7.0

>

>

>

> Here I am again, with almost the same problem, this time with

> VFP 7.0. I'm trying to run an executable created in VFP 7.0

> on a server that uses Windows 2000, and I'm getting the

> library error ("Cannot locate the Microsoft Visual FoxPro

> support library.") I've added vfp6r.dll, vfp6renu.dll files

> to the C:\WINDOWS\SYSTEM32\ and C:\WINDOWS\SYSTEM directories

> on the server (just in case it should be one or the other, so

> you have you first clue that I don't know what I'm doing, I

> suppose). No go.

>

> I also created a directory containing the .DLL files and my

> executable, on the theory that Windows 2000 wanted everything

> in the same place. No

> go. The new directory has been added to the PATH statement.

>

> I'm not using InstallShield, but rather creating the

> executable from the FoxPro project, which has worked for me

> until this problem arose. How can I include the runtime

> files when the executable is created, so that it will run on

> Windows 2000?

>

> Thanks,

>

> Catherine Hines

profoxtech-bounces@leafe.com wrote:

> I'm not using InstallShield, but rather creating the executable from

> the FoxPro project, which has worked for me until this problem arose.

> How can I include the runtime files when the executable is created,

> so that it will run on Windows 2000?

I find the easiest way is to create an setup file using Inno Setup rather

than Installshield. You need to create the exe through teh Project Manager

then store it in a suitable location. If you want to go down that route I

have an example of a script for VFP7, please email me off list and I'll send

it. There are more details on

http://fox.wikis.com/wc.dll?Wiki~InnoScripts~VFP. Inno Setup can be

downloaded from http://www.jrsoftware.org/.

John Weller

Wessex Computer Solutions

01380 728880

07976 393631

--

No virus found in this outgoing message.

Checked by AVG Free Edition.

Version: 7.1.375 / Virus Database: 267.14.22/238 - Release Date: 23/01/2006

Inno Setup works great!

And it's easy if you also download the Inno Setup tools. There's a link

at the site for them as well.

It just works!

John Weller wrote:

>profoxtech-bounces@leafe.com wrote:

>

>

>

>

>>I'm not using InstallShield, but rather creating the executable from

>>the FoxPro project, which has worked for me until this problem arose.

>>How can I include the runtime files when the executable is created,

>>so that it will run on Windows 2000?

>>

>>

>

>

>I find the easiest way is to create an setup file using Inno Setup rather

>than Installshield. You need to create the exe through teh Project Manager

>then store it in a suitable location. If you want to go down that route I

>have an example of a script for VFP7, please email me off list and I'll send

>it. There are more details on

>http://fox.wikis.com/wc.dll?Wiki~InnoScripts~VFP. Inno Setup can be

>downloaded from http://www.jrsoftware.org/.

>

>

>John Weller

>Wessex Computer Solutions

>01380 728880

>07976 393631

>--

>No virus found in this outgoing message.

>Checked by AVG Free Edition.

>Version: 7.1.375 / Virus Database: 267.14.22/238 - Release Date: 23/01/2006

>

>

>

[excessive quoting removed by server]

PS: I put the run-time libraries in the same folder as the application's

.exe file.

From what I've heard, m$ recommends that the run-times NOT be put in

the the system folders anyway.

Chet Gardiner wrote:

> Inno Setup works great!

> And it's easy if you also download the Inno Setup tools. There's a

> link at the site for them as well.

>

> It just works!

>

> John Weller wrote:

>

>> profoxtech-bounces@leafe.com wrote:

>>

>>

>>

>>

>>> I'm not using InstallShield, but rather creating the executable from

>>> the FoxPro project, which has worked for me until this problem arose.

>>> How can I include the runtime files when the executable is created,

>>> so that it will run on Windows 2000?

>>>

>>

>>

>>

>> I find the easiest way is to create an setup file using Inno Setup

>> rather

>> than Installshield. You need to create the exe through teh Project

>> Manager

>> then store it in a suitable location. If you want to go down that

>> route I

>> have an example of a script for VFP7, please email me off list and

>> I'll send

>> it. There are more details on

>> http://fox.wikis.com/wc.dll?Wiki~InnoScripts~VFP. Inno Setup can be

>> downloaded from http://www.jrsoftware.org/.

>>

>>

>> John Weller

>> Wessex Computer Solutions

>> 01380 728880

>> 07976 393631

>> --

>> No virus found in this outgoing message.

>> Checked by AVG Free Edition.

>> Version: 7.1.375 / Virus Database: 267.14.22/238 - Release Date:

>> 23/01/2006

>>

>>

>>

[excessive quoting removed by server]