Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Error 'record is not locked' in VFP8 with 'modify memo'
Message
De
08/09/2003 12:17:42
 
 
À
08/09/2003 03:10:42
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00825662
Message ID:
00827148
Vues:
25
Hi,

Some more questions:

How is this action being called? Do you have an older .spr that is running when you call the modify memo? Or is it a vfp form? Are you browsing or is there a grid in place? By what means does the user select the record to be modified when you call your code to edit the memo field? Have you tried an edit box on a form? I didn't realize you were using local views with table buffering--I never do that so I am not the best person to help you with specific questions on that issue.


>Thanks Tracy for answering.
>I'm using a local view with table buffering. ¿How is possible this error en this environment? ¿must i use 'rlock()' in my view? ¿Why before installing VFP8 i didn't need it?
>
>
>>We've used:
>>
>>
>>USE mytable SHARED
>>IF RLOCK('mytable')
>>	MODIFY MEMO mytable.memofield IN screen
>>ENDIF
>>
>>
>>>Since i've installed VFP8 in on customer, modifying memo fields with:
>>>
>>>activate screen
>>>modify memo alias.field
>>>
>>>we get a lot of errors. The most usually are
>>>
>>>'record is not locked'
>>>'"field" is not a file variable'
>>>
>>>¿Any idea? Wih VFP 5 we have no problems with the same exe.
.·*´¨)
.·`TCH
(..·*

010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform