Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Which type of class to use?
Message
From
06/01/2005 02:27:16
 
 
General information
Forum:
Visual FoxPro
Category:
Classes - VCX
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP2
Network:
Windows 2000 Server
Database:
Visual FoxPro
Miscellaneous
Thread ID:
00973101
Message ID:
00974611
Views:
26
Yes I did slightly miss the point. I can see what you are driving at. And it seems a good idea.

There might be some gotchas in trying to make that work for the Fox team. I'm thinking, how do you specify that the result of a query is to remain in the shared session or in the private session? What about alias clashes etc?

What I intended by my reply is that you can rely on datasession 1 always being around, so by switching datasessions you can achieve a very similar result, but of course it's not so nice, and you have to be really careful doing this if a form is around and somehow it gets refreshed, or if a user clicks on a menu and the SKIP condition refers to a table that is no longer there.


>>>What I'd like to see is a global or shared datassession that could be accessed from within many private datasessions. That way system tables could be opened and referenced there and still have the benefit of private datasessions for specific type application data. Closing the private datasession would only close those tables, leaving the "shared" session open.
>>
>>Well datasession id 1 is the "global" session, and sometimes I will simply create a cursor in that session from within a private datasession by using "set datasession " command. Any tables required are simply "use again" so there's no apparent speed penalty.
>>eg say we are in datasession id 5
>>
set datasession to 1
>>lUsed= used('mytable')
>>select * from mytable where <somecondition> into cursor mycursor
>>if ! lused
>>  use in mytable
>>endif
>>set datasession to 5
>>
>>In reality I'd use a few properties to do this more neatly; but you get the idea?
>
>I think you missed my point about "global" data session. I would like to have access to a "shared" session from any private session at the same time, no switching involved. That way, you could join tables or access data from this shared session at the same time as your private session. Only difference is when you're private session goes away, nothing happens to the shared session, it stays around. This is above and beyond the default session 1 area.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform