Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Code works on C drive but not on a mapped Novel drive?
Message
From
11/02/2004 13:07:58
 
 
To
06/02/2004 12:28:35
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Miscellaneous
Thread ID:
00873617
Message ID:
00876345
Views:
20
I thought I responed, but do not see it so I am reposting.
>Hi Claude,
>Just to rule it out: Is there a grid on the form? Where is the focus when you save?

Yes there is a grid which is used for data entry. I assume focus is on the "save" button since it "click" method is being executed.

Have you searched the many Novell optimization messages on the UT? There are many recommended settings for Novell on this forum...
>

I did try searching on "Novell optimization" but did not find any responses in VFP forum. Is that the correct place to look? If so what is a good search phrase? If not which forum should I look at?

>
>
>>I did the following:
>>
>>1. Update my Novell client to 4.90 SP1a.
>>
>>2. Commented out code relate to the RLOCK and add AERROR code to determine what the e
rror is after the TABLEUPDATE command. I get error no 109, Record in use by an other user. I aslo display record no and key field value. It is in the middle of the table being updated. What s strange is that I am the only user.
>>
>>2. If I also comment out the TABLEUPDATE command it works as expected.
>>
>>Any insight appreciated.
>>
>>>>>Ok,
>>>>>
>>>>>Two things...
>>>>>
>>>>>1. If your cursor is table buffered RLOCK shouldn't be in there, since you ar only doing the replace in the local buffer.
>>>>
>>>>The cursor contains the input data which is used to update the table pireq. Should I still remove the RLOCK?
>>>
>>>Yes... I am thinking that since you are locking the record, the update is actually happening there even though you are table buffered, so when you do call table update there are no records to update.
>>>
>>>Since your design is to update the buffer the RLOCK should not be there.
>>>
>>>BOb
>>>
>>>
>>>>
>>>>>
>>>>>2. After you table update fails issue;
>>>>>aerror(MyError)
>>>>>messagebox(MyError[1])
>>>>
>>>>Will try that and myerror[2] for message
>>>>
>>>>>
>>>>>This should tell you why the update failed.
>>>>>
>>>>>BOb
>>>>>
>>>>>
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform