We (in this department) have a small FoxPro executable written in FoxPro

2.6. It's been running fine on a dedicated machine in the customer area

until about six months ago, when the users determined that they needed

to both move it to other desktops and to modify it. We haven't yet

tried to modify it because we can't get it to run on my desktop but

mine, so far. I have VFP 7.0 installed, as well as 2.6.

The new users - the customers - get the error message above, which is

pretty surprising since 2.6 is pre-VFP but I assume it is a Windows

thing. I'm using Windows XP Pro 2002 service pack 2, as are they.

I looked this message up online and found the recommendation to copy two

files (vfp6r.dll, vfp6renu.dll) to c:\windows\system directory of the

desktop with the problem. The tech guy has done that, but is still

getting the error. My desktop has the vfp8 version of those files; the

directory containing the executable that we're trying to run contains

the vfp5 versions.

Any suggestions? We added the directory containing all of the Fox DLLs

to the PATH statement on the desktop, but that did not solve the

problem, either.

Catherine Hines

http://leafe.com/archives/showMsg/213731

Andrew Davies  MBCS CITP

  - AndyD        8-)#

**********************************************************************

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager.

This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses.

Please contact internet.administrators@manchester.gov.uk with any queries.

**********************************************************************

You state the files were copied to the "c:\windows\system" directory. It should be the "c:\windows\system32" directory. Better yet, to avoid having it in the system32 directory, put it right in the application directory.

I don't know if that will help, but its worth a shot. Is it possible you (or they (rolling eyes)) compiled the program with version of VFP ? Cause I don't know why a FPD/FPW 2.6 app would be looking for a VFP support library. My suspicion is someone there is busy trying to 'update' it and has just enough knowledge to be dangerous.

John G.

-------------- Original message ----------------------

From: "Hines, Catherine" <catherine.hines@lmco.com>

>

> We (in this department) have a small FoxPro executable written in FoxPro

> 2.6. It's been running fine on a dedicated machine in the customer area

> until about six months ago, when the users determined that they needed

> to both move it to other desktops and to modify it. We haven't yet

> tried to modify it because we can't get it to run on my desktop but

> mine, so far. I have VFP 7.0 installed, as well as 2.6.

>

> The new users - the customers - get the error message above, which is

> pretty surprising since 2.6 is pre-VFP but I assume it is a Windows

> thing. I'm using Windows XP Pro 2002 service pack 2, as are they.

>

> I looked this message up online and found the recommendation to copy two

> files (vfp6r.dll, vfp6renu.dll) to c:\windows\system directory of the

> desktop with the problem. The tech guy has done that, but is still

> getting the error. My desktop has the vfp8 version of those files; the

> directory containing the executable that we're trying to run contains

> the vfp5 versions.

>

> Any suggestions? We added the directory containing all of the Fox DLLs

> to the PATH statement on the desktop, but that did not solve the

> problem, either.

>

> Catherine Hines

>

>

>

>

[excessive quoting removed by server]

Hummm, Lamar, FWIW,

I don't have that file (foxw2600.esl) in my system. The only two fox systems

I have installed are VFP9SP1 and FPW26a.

----------------------------------------

** PabloSr

** DevDBFox

** In a learning adventure!

-----Original Message-----

From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com] On

Behalf Of LAMAR FRAZIER

Sent: Wednesday, December 14, 2005 8:26 AM

To: profoxtech@leafe.com

Subject: Re: "Cannot locate the Microsoft Visual FoxPro Support Library"

If this is FPW26 I believe you need the 2.6 runtime library

(foxw2600.esl) to run this. Try copying it into the folder where the exe is

located. Hope this helps.......

Lamar Frazier

Mississippi Development Authority

lfrazier@mississippi.org

[excessive quoting removed by server]

That's the most likely reason. I never had to distribute an executable as

the program was always run from the development machine.

Thanks!

Original Message:

-----------------

From: LAMAR FRAZIER LFRAZIER@mississippi.org

Date: Wed, 14 Dec 2005 13:05:04 -0600

To: profoxtech@leafe.com

Subject: RE: "Cannot locate the Microsoft Visual FoxPro Support Library"

PabloSr, I am guessing you have the ablility to generate FPW26a

executables via the distribution kit. When I distribute a FPW26a

executable this file is required in order for it to run.

Lamar Frazier

Mississippi Development Authority

lfrazier@mississippi.org

>>> privera1@nycap.rr.com 12/14/2005 12:17:20 PM >>>

Hummm, Lamar, FWIW,

I don't have that file (foxw2600.esl) in my system. The only two fox

systems

I have installed are VFP9SP1 and FPW26a.

----------------------------------------

** PabloSr

** DevDBFox

** In a learning adventure!

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

** All postings, unless explicitly stated otherwise, are the opinions of

the author, and do not constitute legal or medical advice. This statement

is added to the messages for those lawyers who are too stupid to see the

obvious.

--------------------------------------------------------------------

mail2web - Check your email from the web at

http://mail2web.com/ .

Hi Catherine,

Ya need to make sure that you have the foxw2600.esl file located in the same

folder/directory where you want the app to run. Just ran a quick test and I

get the same message if I rename to something else...

I believe that will do it...

HTH,

Regards,

Desmond

>From: "Hines, Catherine" <catherine.hines@lmco.com>

>Reply-To: profox@leafe.com

>To: profoxtech@leafe.com

>Subject: "Cannot locate the Microsoft Visual FoxPro Support Library"

>Date: Wed, 14 Dec 2005 08:22:40 -0500

>

>

>We (in this department) have a small FoxPro executable written in FoxPro

>2.6. It's been running fine on a dedicated machine in the customer area

>until about six months ago, when the users determined that they needed

>to both move it to other desktops and to modify it. We haven't yet

>tried to modify it because we can't get it to run on my desktop but

>mine, so far. I have VFP 7.0 installed, as well as 2.6.

>

>The new users - the customers - get the error message above, which is

>pretty surprising since 2.6 is pre-VFP but I assume it is a Windows

>thing. I'm using Windows XP Pro 2002 service pack 2, as are they.

>

>I looked this message up online and found the recommendation to copy two

>files (vfp6r.dll, vfp6renu.dll) to c:\windows\system directory of the

>desktop with the problem. The tech guy has done that, but is still

>getting the error. My desktop has the vfp8 version of those files; the

>directory containing the executable that we're trying to run contains

>the vfp5 versions.

>

>Any suggestions? We added the directory containing all of the Fox DLLs

>to the PATH statement on the desktop, but that did not solve the

>problem, either.

>

>Catherine Hines

>

>

>

>

[excessive quoting removed by server]

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]