Was connecting to DB on enet LAN installed X and FM tells me file wasn't closed need to recover blah blah. It tries but then quits and tells me something about not locking the file.

Anybody?

Could you try the question again with all the words left in?

-bd

I'm running OS X with FileMaker and it had no problems connecting to a hosted database. Are you connecting to a FileMaker Server, or are you connecting to a local machine via the data access companion?

I apologize for the slang, Let me try again. I am not running Filemaker Pro Server. I have the database on a local server to which myself and 3 other people sign on to use the databases. When I launch FIlemaker Pro 5.0.3 it launches fine in Classic. I then attempt to open the shared databasee on the server and FMPro informs me the the file was not closed properly (it is already open on the server) and then attempts to see if it can revover the file before it gets to the revovery it presents me with a dialog box with the following text.

"MWC Estimate cannot be opened as read-only in its current state. Please unlock the file and open and close it before attempting to lock the file again."

The dialog box includes an "OK" button to dismiss and then nothing back to FMPro.

I can open the same file when I move it to my local machine but that defeats my purpose.

Hope this is clearer thanks for the help.

quote:

---

Originally posted by Dan Gabrielson:

launch FIlemaker Pro 5.0.3 it launches fine in Classic. I then attempt to open the shared databasee on the server and FMPro informs me the the file was not closed properly (it is already open on the server) and then attempts to see if it can revover the file before it gets to the revovery it presents me with a dialog box with the following text.

"MWC Estimate cannot be opened as read-only in its current state. Please unlock the file and open and close it before attempting to lock the file again."

---

AHHHHH You my friend are double clicking on the file from a shared folder, or navigating to the file in a shared folder via the open dialog no?

This is bad news.

You always want to use the File->Open->Hosts method to open shared files.

Differences in file systems, "network operating systems" and various lan configs can cause opening a file directly off a shared folder to exhibit strange behavior, speed degradations and real file corruption.

Use a dedicated host, or instruct everyone to always use File->Open->Hosts first before navigating to the file. Only when the file is not listed in the host dialog should they open the file directly, and only the first person to "open" the file (each day) needs to do this.

Hope this helps!

-Dave

Well I tried to connect via "FIle/Open/Host" but nothing shows up in host box. I might ad I have been doing it by opening the file on a shared folder/volume for over a year. Never had probs. I still can open the file if I boot into 9.1. I also can get at it from other machines not running MacosX. Just not in "Classic" mode under osX

OK so I went back to FMPro to make sure all was set correctly. I changed back to TCP/IP networking then all databases show up under open/host. Problem solved I can connect to all shared db's. Thanks soo much for the help. I have been using MacosX since Saturday and this was the only issue I have had. Just proves how great Mac users are. I appreciate all the help.