Running Fox Exe's from a local network, VFP5.0 vs VFP6 - 8

I have several small office applications written in Foxpro. Years ago I bought some of them up from Foxpro 2.6 & FPW 3.x into the what was then the newest 'Foxpro', 5.x, and then wrote a few more apps. When later on 6.0 had been out for a while I tried to move up to that version. To that point all I had to do when distributing an application was to put the exe, two Dlls, DBFs and a few other files in a directory on the local network protected by the appropriate NT security. Then put an shortcut on the users desktop pointing that exe. With lots of changes in our office responsibilties this is easy to connect new workstations to these apps. With 6.0 that all changed to have to setup the apps on each computer even though the exe and dbfs could be shared on the network. This is what I had to do with VB apps (which is one among other reasons I didn't use VB alot).

I tried to putting all the files the 6.0 setup wizard was putting on each computer on the network in the exe's directory but it didn't work. I guess this is because of the files not being registered properly in the setup. I was hoping that Foxpro would just look for these files in that directory first without checking the registry

The upshot of all this is that all the apps are still on 5.x . I suppose that I could set up one VFP 6.0 app on each workstation and then as long as the rest of the apps used the same componets they would not require an individual setup.

Before I go that route I'm wondering if there is a way to run 6.0 ( or actually I have 7.0 now) the way that I ran the 5.x apps on the network ??

Leemi
Wed Mar 03 13:33:05 CST 2004

Hi:

When you say it "don't work," what error message do you receive?

If you have VFP 7.0, you should be able to do one of the following:

1. Place all the runtime files (VFP7r.dll, VFP7renu.dll, and Msvcr70.dll)
in the same folder on the network as the EXE and start the EXE with a
shortcut.

Or

2. Place the EXE and data on the network, and place the runtime files
listed above on each workstation in the Windows\system32 folder. You can
then point ot the EXE on the network with a shortcut from each local
machine.


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


>I have several small office applications written in Foxpro. Years ago I
bought some of them up >from Foxpro 2.6 & FPW 3.x into the what was then
the newest 'Foxpro', 5.x, and then wrote a >few more apps. When later on
6.0 had been out for a while I tried to move up to that version. To >that
point all I had to do when distributing an application was to put the exe,
two Dlls, DBFs and >a few other files in a directory on the local network
protected by the appropriate NT security. >Then put an shortcut on the
users desktop pointing that exe. With lots of changes in our office
>responsibilties this is easy to connect new workstations to these apps.
With 6.0 that all changed >to have to setup the apps on each computer even
though the exe and dbfs could be shared on >the network. This is what I had
to do with VB apps (which is one among other reasons I didn't >use VB
alot).

>I tried to putting all the files the 6.0 setup wizard was putting on each
computer on the network >in the exe's directory but it didn't work. I
guess this is because of the files not being registered >properly in the
setup. I was hoping that Foxpro would just look for these files in that
directory >first without checking the registry.

>The upshot of all this is that all the apps are still on 5.x . I suppose
that I could set up one VFP >6.0 app on each workstation and then as long
as the rest of the apps used the same componets >they would not require an
individual setup.

>Before I go that route I'm wondering if there is a way to run 6.0 ( or
actually I have 7.0 now) the >way that I ran the 5.x apps on the network ??

anonymous
Wed Mar 03 13:51:07 CST 2004

i think you upper to vfp8.0, and activate the log, if you actualice your aplication and need actualice in the client, the vfp8 is the solution, in vfp8 you have commands for give the version, and you can cuestion if the version is plus then run auto setup. in vfp 8.0 you have the "installshield express"