On Thu, Jul 16, 2015 at 3:09 PM, Ken Dibble <krdib...@stny.rr.com> wrote:
> > Is there some other quick test I should use? > I did put in a request years ago for MS to add a "BROWSE FOR CORRUPTED()" but MS thought it would be too hard. A real problem with a bit set in the wrong place is that you won't trip over it until you reproduce the exact sequence that causes it. Nothing quick is likely to find something hidden this deep. PACK can carry the problem around, as well as REINDEX. It's not quick but rebuilding tables and indexes from clean source can root out a problem sometimes, but at a high cost in effort and downtime. Hence, why people buy tools like Stonefield. Doug's already done the heavy lifting. > Okay. Somebody else said SELECTs operate in their own data session. I think Laurie meant something else. In this case what I mean is this, starting from a fresh VFP session: create table temp (field1 c(10), field2 date) use && no tables open select * from temp into cursor notsotemp select 0 use temp && File is in use! If you run DISPLAY STATUS, you'll see Temp is open, (Readonly) Alias: NOTSOTEMP USED("temp") returns .F. since the table is aliased, even though that might not have been your intent. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: ProFox@leafe.com 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/cacw6n4ssevqclkvdt7asfz6hk3ddtrb4mxq0qxtn77qxdtp...@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.