>I've got a weird situation. Hoping it'll ring a bell for someone. A client has an application based on the Mere Mortals framework. In the midst of doing a large processing piece (not sure how large overall, but the repro up to the error takes 45-60 minutes), it fails with error 1113.
>
>The line that's triggering the error is a Requery() of a local view. Immediately before the Requery(), I've added code that confirms that the view itself is open. (And I just checked: the error that shows up when you try to Requery() a view that's not open isn't 1113.)
>
>This error occurs after processing tens of thousands of records from a cursor. It's reproducible, always failing on the same record. But as I said, it's a cursor, so table corruption seems extremely unlikely. Also, the client says that it reproduces only with the EXE, not in the IDE. I haven't tested this case because I don't know the app well enough.
>
>Anybody ever run into 1113 and have any ideas?
>
>Tamar

I've been opening all the tables at the start of the app IIRC just to avoid such errors. The view will attempt to open the files it needs when they are not open. Since yours is running for a long time before crashing, I'd have guessed that's not the problem. But, maybe part of the view is reading some files and then a UNION SELECT starts reading previously unopened tables? So, if you can, open all tables before running that view.