Information générale
Catégorie:
Gestionnaire d'écran & Écrans
Jim,
So should one surmise that CURSORSETPROP() operates on something totally independent of any tables/views initial property settings as they may be set by DE processing or (manually) elsewhere?
Could I not issue CURSORSETPROP() to set the buffering and expect the MULTILOCKS to already be set properly, assuming that I issued CURSORSETPROP() *after* DE.Init? I know I can try for myself, but my point is to show that the docs may, indeed, be more deficient than you accept.
Jim N
>>Hiya Jim ----
>>
>>>
>>>I ran tests wioth debugout and found that multilocks is set to ON between the opentables and the Init of the DE.
>>
>>So what does this mean? I'm still confused :-D
>
>John,
>
>it means that if you set a buffer mode in the Data Environment of a form or report, VFP will automatically handle the multilocks setting for you without your needing to explicitly set it on. If you set a buffer mode with CursorSetProp() you must first set the multilocks on or the cursorsetprop() call will have an error.
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement