>Hi,
>
>The error (in the title of this thread) is the worst and most dreadful since it is not caused by a bug or bad code but rather the issue with the PC memory (as far as I know). I used to think that the error only happens when the app opens an external DBF file. But lately I see these error (emailed from the app) on attempting to USE/OPEN a DBF included in the .EXE
>My usual suggestion to a customer coming across this error is to reboot the PC.
>Any other suggestions on troubleshooting this error?
>
>TIA
I can't duplicate the Invalid Seek Offset error. But can I throw an exception where the CATCH of the TRY-CATCH would see it as error 1103 (Seek Offset)? I am reading the THROW topic of the VFP help but can't figure out if I can do what I want.
Let me know if it can be done.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham