> Most of the time we have to modify reports or add new options at user end. Thus we have to install VFP at User End.
>
> Rgds:
> Ahsan Rana
Ahsan,
You should NOT install VFP on the user machines for two reasons.
1 - Read the license and you will find that this is in fact, prohibited. You may only distribute your EXE and the runtime files. You may not distribute VFP without purchasing an additional license for each user.
2 - If the users have access to the VFP IDE, what is to stop a user from modifying your app? The user does not actually have to know how to program in VFP to cause you grief - all the user needs to do is cause the app to error out and you will be left holding the blame. It also gives the user the ability to use BROWSE.
You do not need to install VFP on the user machines. Uninstall it immediately and then install the runtime files only. I have a little "Hello World" exe that I install along with the runtime files using Install Shield. The Hello World exe is use to test the install and is then deleted. Using the runtimes only, you can still allow the user to create/modify his/her own reports etc. You do have to write a program to handle this, but it is entirely doable - without installing VFP on the user machines.
Ken
You shall know the truth - and the truth shall set you free. (John 8:33)