Periodically it gives an error "Invalid Seek Offset", which when you look
it up in Help says "Record your recent actions while using VP and then call
Microsoft Support".
I've checked out the known bugs, but this doesn't appear.
There doesn't seem to be any pattern in when the error occurs, and the Seek
it happens on isn't always the same. The files are all OK. If you restart
the system after the crash and repeat the analysis it was doing when it
fell over, everythings fine.
I've got a feeling its some funny in the run time system and/or Win95.
Anybody got any ideas??
Regards
Malcolm Sheldon
About a year ago, I had the same problem with FoxPro 2.6/Windows and
Windows 3.1. It was occurring when the application would perform a SEEK in
some cases. At the time I wrote down three possible cuases in my journal...
#1 Corrupted indexes, .EXE, or run-time file.
#2 Insufficient memory resources
#3 File sharing or problems with the network connection
It was eventually corrected, but I don't know what solution worked.
Malcolm Sheldon <ang...@ada.aust.com> wrote in article
<01bc5b6d$478b36c0$75136ccb@video>...