Preventing users from trashing databases

[jonben]

We have a production database of about 35 related files. Yesterday, someone on the network threw away the "main" database and I was forced to restore from the previous day's backup.

Here's my question. Is it possible to make the files "invisible" to users while still giving them access to the files. I know it is possible to access Filemaker Server without being logged onto the actual server volume by using the "Hosts" button. However, with most of our users, the process of using the "Hosts" button may be difficult to remember. Is there a script or some other automated procedure that could make it a quick procedure?

Thanks for the info.

[pjhodge]

We distribute a "short-cut" database to our users that automatically opens a particular served database from the server. The "short-cut" db contains no data just a script that is launced on opening that opens the target db then closes the "short-cut" db.

I also set sharing to "Multi-User (Hidden)" and open them with status as hidden for db's that have to be open but don't have to be visibile.

--phil

[easyaspi]

This implies that either;

a) anyone can sit down at the server without entering a username and password OR

: you have file sharing turned on at the server

You must disable file sharing on the server. The only acceptable way to open a hosted FileMaker file is by using the Hosts button in the Open dialog.

This process can be scripted. Just make a new file with one script called Open. Add the Open File script step to the script, and when you are prompted to find the file, use the HOSTS button to locate it. Then add the Close script step.

This is not a shortcut or an alias.

Mark

[Keith M. Davie]

"Is it possible to make the files "invisible" to users while still giving them access to the files."

Yes, it is. Custom Web Publishing your solution.

Otherwise consider an opening script which includes the command Allow User Abort [On]. If you don't understand scripts (you are listed as newbie0, you would be well advised to consider getting Scriptology. It is very useful.

[Tom England]

pjhodge,

what do you mean by "and open them with status as hidden for db's that have to be open but don't have to be visibile."??

Thanks

[IdealData]

If you're on FMP 5.5 then you can open files through a web browser by using the fmp5: protocol (as opposed to http) like this:

fmp5://12.34.56.78/filename

(12.34.56.78 = ip address of your fmserver machine)

You could keep this as a shortcut in your web browser.

Maybe some training for users on accessing the files through hosts is more appropriate though.

[pjhodge]

For a few of our db systems there are separate user inteface and data storage files. The databases that have to open buy not visible are ones where data is stored but users don't directly edit. All editing in the storage files is done through relations, scripts or importing.

The only visible database is the UI database with a single window. Which helps to prevent a cleaner interface to the users.

--phil

[Vaughan]

It sounds like you are letting people access the databases through file sharing. This is a *very bad* way to share databases -- corruption is guaranteed.

The preferred way is to set up one machine as a dedicated FMP host, with FMP (or better FM Server) running with all the shared databases opened. People access the files through the Open Remote command in FMP.

Disable file sharing on this host machine, or at the very least allow file sharing only for administration.

If using the hosts button is too hard to remember, either create an opener file for them (a small database that lives on the user's machine, whose job is just to connect to the host and open the remote database, then close) or get smarter users. Seriously. Fixing up corrupted databases through file sharing -- and setting up a host to stop it from happening again -- is bread-and-butter work for most FMP consultants.