First of all look into http://support.microsoft.com/support/kb/articles/Q125/5/76.asp.

Also search MSDN Library for exact phrase "Record not available". Other articles may give you valid advice too.



>Hi all:
>
>The Department that I work for has an application written in Fox 2.6 that has been in existance for several years. The application is comprised of several prorams, menus, and data tables. On an average, between 100 - 150 users are logged in at any one time. We all operate on WIN95 platform.
>
>For the last two months, we have had increasing difficulty using the app. Users will try to save records, but get a scrolling message that says "Record not available..." in the corner of the screen. After watching this scrolling message for 20 - 30 minutes, users get frustrated and shut down the application. Our standard answer has always been to kick everybody out of the system and reindex the tables before allowing access back into them. This used to solve our problems. However, we are starting to go through this process almost on a daily basis - sometimes even twice a day. All of our "experts" are at a loss as to how to handle this. (Rewriting it is an obvious choice, but doesn't solve our short-term problem.)
>
>Users can view information or run reports without generally having problems. The main tables contain over 100 thousand records each. When we examine the records that are getting these error messages, we find that the changes requested are written to the tables, but then the user is stuck in limbo.
>
>Does anybody have any suggestions on directions we can look to for short-term solutions?
>
>Thanks so much for any ideas you might have.
>
>Kim Hughs
>IL Dept. of Revenue