Can't wait to find out who plays you in the movie. Quite the novel. I've skimmed, but can't possibly comprehend, all 20 pages.
If this is production code you have had in production with many people using it for a long time, it's unlikely they just found a new way to break it. So my first inclination is to start with the theory that the code is sound, but something has recently changed: General guidance I'd give would be: 1. Test all data files, index and data contents for corruption. Then source code, too: SCX/VCX/FRX get corrupted sometimes. 2. Review the last code change you made before the problems surfaced. That might have broken it. 3. If it's not the software, perhaps it is the environment. You mention an increasing number of users. That means new machines, OEM configured, with settings that make VFP file sharing annoying to impossible. I'll bet you would have mentioned if new users were the only ones getting this error, though. There's a lot of ways a File Is in Use can sneak into the code. A SELECT will open a filtered view of the table, aliased to the name of the cursor, for example. For the time being, you might consider patching the code with AGAIN on each USE to avoid the error and give you some more time to track down the source. If I understand correctly, the big picture logic is that the user tried to search for a person, executing a SQL SELECT statement via macro, something went wrong, the app shuts down (you claim the user has to have hit the 'X' to close the window?), the app checks to see if all users are logged off and if so, goes into a backup and maintenance routine in which the "File is in use" error trips. Did I get that right? If the user hit the 'X' during a query (how long do these take?) perhaps you need to address this problem. Lock the window so they can't close in the middle, or give them a "Cancel" that doesn't involve application shutdown? My suggestion is that if the app is shutting down on an error, shutdown. Lots of "stuff" gets left over in memory when an error trips, and it's nearly impossible to clean up every possible setting set awry. On Thu, Jul 16, 2015 at 12:40 PM, Ken Dibble <[email protected]> wrote: > >> I'm about to post a very long message providing excruciating detail about >> this. > > > Which, apparently, is hung up in the spam filter. *sigh* > > If anyone would like to read it, it's at: > > www.stic-cil.org/CILData/Error 3.rtf > > Thanks. > > Ken > [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/cacw6n4s5b6kapxmdhdwzlijts7f32kdk0m1xr1g_61fzz6r...@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.
