Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Data not UNLOADing on RELEASE of form
Message
De
30/03/1998 15:36:59
Michael Haggerty
Blue Mountain Data Systems Inc
Herndon, Virginie, États-Unis
 
 
À
29/03/1998 23:17:12
Information générale
Forum:
Visual FoxPro
Catégorie:
Client/serveur
Divers
Thread ID:
00087984
Message ID:
00088204
Vues:
28
>I am having a problem with a form that has a PRIVATE DATA SESSION set but no data being stored in the data
environment of the form. I load remote views and cursors by setting the datasession id to the one of my form. But on
release of the form the data does not get released and gives me a GPF when I attempt to leave VFP via a
SQLCANCEL().
>
>Any help greatly appreciated.
>
>Michael Haggerty

>> Could you be a little more specific by providing details of what you are >>trying to do? A form with a private datasession
>> who subsequently has its datasessionid set to another form's sounds more like >>(in functionality) using a default
>> datasession. If you have nothing in the DE, why are you using Private a DS?

In my form I have three grids, whose data are based on who logs into the system and other params. The use of the private data session is to allow us at a later stage to allow the user to have multiple instances of the same form, but with different data displayed. The reason I create my cursors using my forms datasessionid is so that when the form closes, so will the cursor.

>> What specifically do you mean that the data is not released when you release >>the form? Do you mean the tables aren't
>> closed automatically? This could be for any one of a number of reasons.

If I query the datasessions using AUSED() I see a datasession with UNKNOWN that has tables in it from my form, even though my form has been released.

>> SQLCANCEL is not a command to leave VFP, it is to cancel an executing query. >>I can't say why it causes a GPF, but
>> this is why it doesn't leave VFP. If you want to exit VFP, try QUIT, and if >>you want to close a table try USE or
>> CLOSE TABLES ALL.

I know what you are saying about SQLCANCEL, and it is a correct statement. Because I have remote views attached to my datasession that are not being released when my form is being released, the SQLCANCEL line GPFs all the time. And I do a QUIT after my SQLCANCEL. I dont want to do a CLOSE TABLES ALL, because we share a connection to ORACLE thru a remote view in the default datasession. I may have to use a USE dbfname to close but I would like to know the answer.

Michael Haggerty
amkhag@erols.com
haggertm@pwba.dol.gov
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform