>We are having a lot of problems with the system locking once or twice a day. We have a VFP 6.0 front end with Sql Server 7.0 on the back end using mostly remote views and some occasional sql passthru. Up to a couple of times a day, our users all freeze. When they do, we look at the database .dbc file and view locks with WINFILE, we usually find someone with a lock on the .dbc file that doesn't want to release. As soon as we tell WINFILE to knock off the person with the lock, everyone else starts moving again.

I don't have any suggestions on this bit, I'm sorry.

>We were told that we should be able to set our .dbc file to read-only.

Dunno who told you exactly, and I was surprised, but I just tried it and yes, I could set the DBC, DCX, and DCT to ReadOnly and I could still open the database and manipulate data. I wasn't able to edit stored procedures or see the RI, as I'd expect. So, is "OPEN DATA DB/SYS SHARED" done in the right directory for that relative path to work?

FWIW, it seems like the first problem really needs solving. Perhaps it's a network problem? What sort of network is it? Do you have all the latest service packs for VFP, SQL Server, and the network? Is the person with the lock always the same?