Stephane,
I think you should read more on the Windows Installer Technology. You may find that the Operating System will defeat your efforts, and I think that is why we are using updated methods of Setup - from W2K onward life has changed in the Install department. At the very least you may be creating unstable conditions on the client machines - and VFP might end up getting the bad name instead of the rogue who ignored the correct way of updating your client machines.
Set Rant OFF
HTH
Regards
>Never Mind, i found my answer, it turns out the msvcrt70.dll can be renamed. After renaming it, i can freely copy the new file so it will be used the next time VFP Starts. Here's my code
>
>

>Declare Integer CopyFile In Win32Api String, String, Integer
>Declare Integer MoveFile In Win32Api String, String
>
>=MoveFile( lcFile, lcFile + ".OLD" )
>=CopyFile( lcNewFile, lcFile, 0 )
>

>
>>I have a VFP 7 exe installing an upgrade to VFP8, i install and register everything fine, but when it comes to msvcr70.dll i can't replace the file because it is in use by my VFP 7 update program. The msvcr70.dll is in the \winnt\system32 directory.
>>
>>How can i replace this file in a VFP Exe ?
>>
>>Thanks.