What I did in the command window was:

pcAnalyst = 'AREA2A'
OPEN DATA \\MyServer\MyApp\data\crsdata.dbc
SET DATA TO \\MyServer\MyApp\data\crsdata.dbc
USE EMPLOY2VIEW

If I'm the only one accessing the server, I get the results in a second. However, if there's someone who is also accessing the server, I get the results in about 8 seconds. If the other person also uses the same view, I get the results in about 10 seconds. The view is parameterized by Analyst's ID (pcAnalyst).

Besides, if I log into the application and run the form that uses the aforementioned view (along with other tables), just by myself, it takes 10 seconds. If another user is logged on, it'd take a full minute to a minute and half...

Thanks for the URL, I find that very interesting. In that case, what's the purpose of using views in a multiuser environment?!

Furthermore, the problem is not just the views. Launching the application usually takes about 5-7 seconds. But with subsequent users logging in, launching the application takes longer. The application resides in the user's local drive. The CONFIG.FPW is in the application.

Oh, there are no memo fields at all.

>BTW, when you say "opening a view", you mean USE NODATA? Or are you grabbing data too? Is the view in a .DBC on the server and is it possible 2 or more people are using this view at the same time?
>
>See http://fox.wikis.com/wc.dll?Wiki~CreatingDBCforViews~VFP for more info...
>
>Jim's correct, unless you are doing some really weird and complex stuff or your 1,000 record table is chock full of *huge* memo fields, it shouldn't take even 1 second to open a view.
>
>Are the tables that make up the view open before using the view? If they are not, there may be a delay opening one or more of the underlying tables.
>

Thanks!
~d
J