>>There is no reason to not go with VFP 6.0. Make sure you download and apply service pack 3. 6.0 is more stable than 5.0 and has lots of bug fixes.
>
>Craig,
>I realize that 6.0 will be better, but my problem is time. Last time I tried to install VFP 6.0 is was the beta version from Devcon 98. I got some message about my registry not having enough room. On the M$ knowledge base it said to shorten some of the paths to my applications to make more room in the registry. I tried this and it still didn't install. Have you ever heard of this problem??
Remember...that's a beta version. The release version could give different results. In any event, you can install VFP 6.0 in a different directory than 5.0. I also seem to remember that my registry size was increased when I installed VFP 6.0.
>
>Since then I got the 6.0 upgrade disk, but haven't installed yet, fearing the same problem, and realizing that I may have to do some intense disk housekeeping, to resolve it and clean out the registry.
You can download RegClean from several web sites. Look for it at microsoft.com. It will easily clean up the registry.
>
>If my app is going to crash and burn with VFP5 on citrix, I will go through the pain, install VFP 6.0, but doing this will probably cause me to miss the client's deadline. But if VFP 5.0 can handle 6 users on Citrix, I'd prefer to wait a month, then upgrade both myself and the client.
>
>What do you think?
I don't use Citrix, so I can't comment on it specifically. However, unless you use ActiveX controls, 5.0 should be fine.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer