That did it!!! Here's what happened:
Users all have a default folder called \common
They open up tables based on their site \0101 for example.
A DBA had trouble setting up a new user and built a complete set of
empty folders in the \common folder. Even though I am setting the dbc
to \0101\MYDBC in the private datasession, it is opening up views in the
\common\MYDBC. This does not happen on a local PC but only seems to
happen in a terminal services environment.
I discovered the problem by opening up a form with no data in it,
setting the datasession to that datasession as Paul suggested and
issuing a ?DBF() to discover that I was looking at the wrong tables.
I deleted the tables and dbc in the \common folder and everything is
back to normal!
Thanks Paul and everyone else for your help.
Jeff
Jeff Johnson
[EMAIL PROTECTED]
SanDC, Inc.
623-582-0323
Fax 623-869-0675
Phoenix Python User Group - [EMAIL PROTECTED]
Paul McNett wrote:
> Jeff Johnson wrote:
>> My best guess on this is that only one data session is behaving
>> correctly. Additional data sessions appear to be getting confused
>> somehow. Only a guess based on observation.
>
> Test this datasession theory at the command window using SET DATASESSION
> TO and opening your views.
>
> If that pans out, then we can wonder if perhaps VFP doesn't have the
> system resources needed (or something) to properly deal with multiple
> datasessions.
>
> Paul
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
