redzombi19
Programmer
Hi guys I was wondering if any of you know the specific dll files I need to make a program run a computer with out FoxPro already installed?
Thanks,
Steve
Thanks,
Steve
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
required dll's for foxpro 6 distribution
- Thread starter redzombi19
- Start date
- Status
HI
It is always advisable to use the SETUP distribution so that VFP will add all wanted runtime libraries.
However.. here is the list..
VFP6R.DLL or VFP7R.DLL
VFP6T VFP7T
VFP6RENU VFP7RENU
MSVCRT*
ramani
(Subramanian.G),FoxAcc, ramani_g@yahoo.com
It is always advisable to use the SETUP distribution so that VFP will add all wanted runtime libraries.
However.. here is the list..
VFP6R.DLL or VFP7R.DLL
VFP6T VFP7T
VFP6RENU VFP7RENU
MSVCRT*
ramani (Subramanian.G),FoxAcc, ramani_g@yahoo.com
Mike Gagnon
Programmer
redzombi19
You may also want to read faq184-2644 if you intended to just copy them. Mike Gagnon
If you want to get the best response to a question, please check out FAQ184-2483 first.
You may also want to read faq184-2644 if you intended to just copy them. Mike Gagnon
If you want to get the best response to a question, please check out FAQ184-2483 first.
darrellblackhawk
Programmer
For quick and dirty installs, you can normally just drop the dll's into the same folder that the exe will run from.
I do this a lot for local machines where I don't want or need to perform a professional install.
I've also done it many times on client machines.
MSVCRT (Msvcrt.dll - Microsoft (C) Runtime Library) should already be on the machine. If it's not, you and/or your client will have noticed the effects of it's lack of presence long before you install your app, since almost all windows apps depend on it for their functionality.
Darrell
'We all must do the hard bits so when we get bit we know where to bite'
I do this a lot for local machines where I don't want or need to perform a professional install.
I've also done it many times on client machines.
MSVCRT (Msvcrt.dll - Microsoft (C) Runtime Library) should already be on the machine. If it's not, you and/or your client will have noticed the effects of it's lack of presence long before you install your app, since almost all windows apps depend on it for their functionality.
Darrell
'We all must do the hard bits so when we get bit we know where to bite'
- Thread starter
- #5
"Red",
Also be aware that just copying and registering the VFP .DLLs may cause an unstable environment on some systems - especially older OS's or those systems that are not kept up to date with the MS updates. A specific VFP .DLL version often requires a certain update level of other OS support files (sometimes different on different OSs!), and if they are unavailable, strange things may happen in your VFP app. There really are reasons to use the supplied Setup Wizards so you make sure all the pieces are updated properly.
Rick
Also be aware that just copying and registering the VFP .DLLs may cause an unstable environment on some systems - especially older OS's or those systems that are not kept up to date with the MS updates. A specific VFP .DLL version often requires a certain update level of other OS support files (sometimes different on different OSs!), and if they are unavailable, strange things may happen in your VFP app. There really are reasons to use the supplied Setup Wizards so you make sure all the pieces are updated properly.
Rick
- Status