I'm using the browse screen as a pick screen. The user select a record they want to work on and hit escape, and the system brings her to that screen. It really doesn't have to be a current up-to-the-second. If this fixes it, them i'm done, if not, then I can just rewrite the browse screens and make them grids, and that would fix it too. I could just create a temporary cursor and do the same thing. ----- Original Message ----- From: Mike Copeland <[email protected]> To: [email protected] Cc: Sent: Wednesday, April 18, 2012 3:21 PM Subject: Re: 2066 errors - solved (I hope).
Excellent detective work! I know it's not a lot of help without a major rewrite, but I would recommend that instead of browsing through the live data files, sql-select the data set you need, then present it from a local cursor, then write back any changes and discard the rest. As you have found, if you have multi-user access to the same records, then someone has to deal with the changes that "Bob" made and stored while "Susy" was accessing, and possibly changing, the same record. It sounds like you have been relying on VFP to handle that for you...updating the browsed data that may be displayed on a different workstation? That's pretty risky business. If I'm misunderstanding, my apologies. Mike Copeland -------- Original Message -------- Subject: 2066 errors - solved (I hope). From: Michael Madigan <[email protected]> To: [email protected] Date: 4/18/2012 2:11 PM 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. [excessive quoting removed by server] _______________________________________________ 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. _______________________________________________ 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.
