After much searching on the net, I came up with what I think is causing the issues.
1. If you have Win 7, VFP 9.0 and a browse screen in your application, VFP can report phony 2066 errors and/or create real errors. Apparenly VFP is more "picky" when it comes to changed data, so if two users are browsing a screen, even if the browse screen is not editable, when one of the items on the screen is changed from another computer it can cause VFP to think the index is out of synch. The solution I've tried is to set the refresh to 1,1 rather than the default 0,0 and so far today, since 9:00 AM, no errors. This is also the recommended solution if you are using VFP OLE provider http://support.microsoft.com/kb/947664 Apparently it's now a no-no to use browse screens in multi-user environments, even though application has run for years and years. _______________________________________________ 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.
