Welcome To The Home Of The Visual FoxPro Experts  
home. signup. forum. archives. search. google. articles. downloads. faq. members. weblogs. sponsors. rss.
 From: Pete Sass
  Where is Pete Sass?
 Marathon, Ontario
 Canada
 Pete Sass
 To: venkataramesh cheruvu
  Where is venkataramesh cheruvu?
 hyderabad
 India
 venkataramesh cheruvu
 Tags
Subject: RE: Error NO130
Thread ID: 232929 Message ID: 232937 # Views: 32 # Ratings: 0
Version: Visual FoxPro 9 Category: Errors & Debugging
Date: Saturday, June 27, 2009 7:59:36 PM         
   


> Hello Experts
>
> Please guide me about Error #130.
>
> I am assigned a job of completing an user interface which was 80% done by my predecessor. The current process involves 4 forms (private data session, buffer=5) all of which have one particular table 'orderhdr' in common and with other different tables/views/relations. All the three forms are to remain in memory and when I issue tableupdate() in the 4th form on a view, this error gets fired. The process was designed to allow the user to navigate to and fro quite frequently and performs numerous calculations. Considering a change now is not allowed.
>
> I have checked up the help but could not get enough information. Please tell me why at all the error fires? What could be possible fixes?
>
> Thanks,
> C.V.Ramesh


Afternoon from Canada,
Gnerally this error happens when you try to update a record and the record is not locked. Can happen when
performing; BROWSE, CHANGE, EDIT, DELETE, GATHER, MODIFY MEMO, READ, RECALL, or REPLACE operations.
Are you 100% certain your have buffer mode-5 in all forms and you have private data sessions in all forms?
Pete "the IceMan", from the Great White North of Canada.



COMPLETE THREAD
Error NO130 Posted by venkataramesh cheruvu @ 6/27/2009 4:21:53 PM
RE: Error NO130 Posted by Pete Sass @ 6/27/2009 7:59:36 PM
RE: Error NO130 Posted by venkataramesh cheruvu @ 6/28/2009 5:46:45 AM
RE: Error NO130 Posted by Borislav Borissov @ 6/27/2009 8:57:04 PM
RE: Error NO130 Posted by venkataramesh cheruvu @ 6/28/2009 5:57:39 AM
RE: Error NO130 Posted by Stefan Wuebbe @ 6/28/2009 9:22:17 AM
RE: Error NO130 Posted by venkataramesh cheruvu @ 6/29/2009 3:31:11 PM