Kevin Cully wrote: > I've seen some intermittent problems solved by putting a "SELECT > csrTrans" between the SELECT and the INDEX ON statement. > > In addition to that, you could put an ORDER BY Transdate in the SELECT. > If they're using this table for viewing records, (and not SEEKing or > LOCATEing) then the result may be the same as creating the index. > > In addition to that, and I'm not sure what version of VFP you're using, > but you could wrap the INDEX with a TRY .. CATCH. > > Just my $0.02. Believe it or not, I'm most hopeful about just putting > the SELECT csrTrans between the statements. It seems to force VFP to > straighten out the work areas for me. > > -Kevin > CULLY Technologies, LLC
Yep...I follow the same practice as you. Whenever I'm in areas of code being checked out and modified, I don't mind adding these kinds of things so that they're taken care of in the next release. I agree with your approach for being proactive in the future...just like I always use the IN clause when possible (e.g., REPLACE LastName with "Cully" in MyTable). _______________________________________________ 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.
