Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Thanks for yr guidance...
Message
From
05/03/1999 12:32:49
 
 
To
05/03/1999 12:15:37
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00194574
Message ID:
00194589
Views:
21
>Thanks for yr reply on Creating EXE files in VFP.
>
>Actually we are developing a software (A Trading Application), for our Group of Companies. And this was the first time our team of Developers are using VFP 6, and we were stuck on this particular issue
>
>And now it seems to be solved.
>
>However, I am facing one another problem, I am receiving some message while I try to run VFP on some machines From the Network. That means, VFP is loaded on the Server, and I am trying to start it from my computer. It gives some error about MSVCRT.DLL file and stops.
>

Nancy's recommendation should be correct - you must install the necessary runtime files on each workstation, regardless of the location of the executable file and data. Simply copying the files to the local machine is not enough; there are shared components such as the MSVCRT libraries that may have to be updated, and some of the VFP runtime components need to make entries in the registry. make certain to download the current patches to the Setup Wizard from Microsft.

>I am using a few Pentium 100+ processors and some 486 DX33 computers with 16 MB+ RAM.
>

Additionally, you will probably need to update any machines running the original Windows 95 retail version to at least SR1 (this can be downloaded from microsfot's Windows Update page for WIn95), and you may need to install other components such as DCOM95 to avoid some known problems with VFP6 as it is distributed now.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform