I have a multi-table database in a single file that references a table in another file via a relationship that I defined. Whenever I open the primary file I am able to access records in the secondary file via the relationship without opening the secondary file and the relationship works as expected. My problem begins when I close the primary file. If someone else opens the primary file they get a message saying the secondary file is in use. Acknowledging this message then brings up the open file dialog window expecting you to open a file to satisfy the relationship. Choosing the secondary file results in the same message. Canceling the message causes the relationship not to work. The only way to close the secondary file is for the original user to exit out of the filemaker application. I created a closing script that uses the close file script step to close the secondary file upon exiting the primary file. But this does not work. The file is still in use when a different user attempts to open the primary file. Is this a bug? Has anyone else experience this? Is there a work around to this?

When two files are related, opening one of the files may result in the other file opening hidden. You can see hidden files listed under the Window under the sub-menu Show Window. For example, let's say you open the first file and display a layout displaying related fields from the second file. In order for FileMaker to display the related data, the second file must be opened. However, the file will open as hidden.

I'm not sure why your close script is not working. Try changing to a layout with no related fields on it in the primary file and then close the secondary file. This should prevent the secondary file from opening again.

However, I have a bigger concern about how you are sharing the file. Why don't you use networking so everyone can look at the file at the same time?

Thank you John Mark for your insight. As you said the file opens as hidden and appears under the window/show window menu. Something I was not aware of. When I close the primary file and look at window/show window the secondary file is still opened as hidden which explains why the next user of the primary file gets the "in use message". Why it does not close with the "close file" script command is still not known and I will research further.

The reason I kept the secondary file separate from the primary file and not "networked" is two fold. First, this secondary file will be used by other future solutions. Second, the five hundred million dollar a year firm I work for is too cheap to pony up the money for FileMaker server.

Edited November 16, 200619 yr by Guest