Hi!

What is the exact command that cause the error? Do you modify the database or database objects structure on the fly in the application? Any word on after what moment database is locked by another user?

>We currently use VFP 6.0 as a front end running Sql Server 7.0 on the back end. We do most of the interaction with the database using remote views. We have been getting quite a few ERROR READING FILE (1104) errors throughout the day. No single spot in the application errors every time. It can happen at different locations in the application. The users who get the error also seem random. One of the most common locations where we get the error is using a view that only pulls 1 record. The view that is used shares a connection. I believe that all views that share that connection have the ShareConnection property set to True.
>
>The properties of this view include the following: ShareConnection = True, FetchSize = -1, MaxRecords = -1, FetchAsNeeded = False.
>
>An addition problem: We may see 10 to 15 of these ERROR READING FILE errors, but maybe once to 3 times per day, the error leaves the user with a lock on the DBC file, locking all of the other users out. Each time we have to get into WinFile and find the user with a lock on the DBC file and knock them out, while every user we have is stuck. This does not help our company's efficiency.
>
>Microsoft has been no help. Does anybody have any ideas what I might be missing?