Anything CAN happen. Depending on record pointers is not a great idea. More info about your particular situation might make the answer more useful.
It's pretty unlikely, with "pure" SQL. But if you include FoxPro functions within the SQL that affect record pointers, or refer directly to open tables/aliases, it's possible for record pointers to move. In addition, if there's anything else going on, like a grid losing focus, that can have a record pointer effect, depending on the state of the data environment(s). Dan says that programs have record pointers; I hadn't thought of it like that. Private data sessions have record pointers. the default data session has record pointers. Sometimes, the internal "work area zero" has its own record pointer, which nearly always is transparent to us. So tell us what you're doing and what you're seeing and why you think SQL is moving record pointers. You might be hitting one of those edge cases. On Thu, Dec 18, 2014 at 9:45 AM, Paul Newton <[email protected]> wrote: > > Hi all > > Does anybody know if executing a SQL Select command/statement CAN result > in record pointers in open tables being moved? My testing seems to > indicate that record pointers are NOT moved but I need to be sure. > > Many thanks > > Paul Newton > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cacw6n4trn8mn5dvokddbfv1zezkqnffz8wvad-zkvfiiqmv...@mail.gmail.com ** 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.
