Probably this was posted before but i need a clarification please

[titoneon]

Hi,
So far while working with vfp 5.0 or 6.0, after creating an Exe application, i always do this as follow
1- if the Exe is going to run from a WIN XP 32bit, i copied the support library into the c:\windows\system32 on that machine and worked fine
2 if the same above is on a machine with windows 7 64bit then the "Supp. Lib.", I put it into the c:\windows\syswow64 and that worked fine for me.

questions 1- for VFP 9.0: if windows xp 32bit then where should be the two support Lib files ?
2- " " : if windows 7 32/64bit " " ?

Just want to know cause i was googleing around and some are saying that should resides in the same folder where the application is running, i don't see anything wrong with that but what about when your application(Exe) is in the server ? i don't think it is a good idea having the "Supp. Lib" in the server folder where the exe, dbf etc resides, just my opinion, please correct me.

 

[Dan Freeman]

You shouldn't have the exe on the server, either. It's the WORST way to configure a VFP app.

This URL will give you the required files and recommended locations.

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

Many people put the support files in the same directory as the EXE. Among other things, it may prevent having them overwritten with another version.

 

[Olaf Doschke]

I agree to dan. The bad idea is to put an EXE on a server, unless it's used local, eg users connect via terminal server and thereby are using the EXE remotely, then the EXE runs local on that server. I don't think that's what you intend to do, though. An installation on a server in a LAN, is not a real installation. You can run many things this way, which don't need registered components (ActiveX controls for example will need to be registered on each local client). But it's not seldom developers doing so report performance problems. It's considered a bad idea therefore.

Creating a setup with Installshield or Inno is making a clean good install for a single end user downloading and installing it like any other software, in a corporate LAN with many users that may be an administratve nightmare, but there is WSUS software update servers for that matter, you can assign software. If a larger company is your customer, they should do it already and know how to distribute your MSI package or setup.exe to all clients needing that software. And beside the cliet software installation you'll typically have a second server side installation of the central database, obviously. It can't be part of the client installation, as there only will be one database for all users. Often enough this is even done administratively manually, by copying DBFs etc to a data share.

Bye, Olaf.