Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Datasession conflict
Message
De
09/11/2018 20:00:04
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows 10
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01663173
Message ID:
01663264
Vues:
110
>"Changing the DataSessionID property setting increments the reference count of the data session changed to and decrements the reference count of the data session changed from."
>
>"However, if you create a data session by setting the DataSession property to 2 (Private data session), changing the DataSessionID property setting does not release the initial data session. In such case, the object must be released to the initial session"

Just to add to what Thierry said, any object created will maintain reference to the datasession in which it was created. Whenever an object's code runs, the DS switches to the one in which the object was created.

>This made me think that there is some way to manipulate the DataSessionID even at the risk of losing the datasources of the object

Worse, you'd further complicate things and the mess will be more complete.

Just use a search tool and find all the places where you set DS to 2, 3 or 4 and replace those numbers with whatever you decide to use to store the actual numbers. This is the simplest way that I see.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform