<snip> > The one that most often bites me is inadvertently changing a field > value, and then trying to move the record pointer without first issuing > an update (and, sometimes, a requery()) Good luck - those messages > drive me mad. I often give up and just rewrite it as a SPT :( <snip>
Vince care to expand on that a little bit more. Because I think this is my problem. So, the order of table events should be: 1. Make modification to updateable field 2. Do a TABLEUPDATE() 3. The move record pointer Does that sound right? v/r //SIGNED// Stephen S. Wolfe, YA2, DAF 6th MDG Data Services Manager 6th MDG Information System Security Officer Comm (813) 827-9994 DSN 651-9994 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
