>I've set up some clients using VFP on Metaframe. In one case we did a trial running the exact same app but compiled in VFP 3, 5, and 6, just to see which one was best. VFP6 won, even prior to SP4.
> The major thing to watch out for is the settings for the VFP temporary files (EDITWORK, SORTWORK, PROGWORK). For a typical workstation you might set all of these to a directory on the C drive for performance reasons. However, if you use ie C drive in a Metaframe environment, all users will point to the same place and you will have potential contention issues. Citrix has an environment variable called RootDrive, which, if implemented, gives each user a private baseline directory. Usually W: unless the system administrator made it something else do to an existing drive assignment. With this, you can set, say, SORTWORK to W:\FOXWORK and it will actually point to a different palce for each user. You would have to create th directory, of course. If you are using an ODBC data source instead of just native Foxpro files, you will probably want to put the connection under the System DSN so it exists for all users.
> Other than that, I've not had any problems running VFP apps under Metaframe, any version.
>
> Randy
>
>>Okay, here is the first question (the second is in the VFP 7.0 folder). I am looking to use VFP 6.0 SP4 in Metaframe XP for a very seriously distributed app, thin client, etc...
>>
>>Has anyone out there done such a task before? And, if so, what problems may I expect?

Randy,

Thanks for the response. It has been in my inbox and I don't know how I missed it. As we are on 'trial' next week I can now address that issue in advance. Thanks heaps!!

Ric