I've been serving from just a client version of Filemaker for the past year, but just bought my first copy of Filemaker Server and so far I like it. However, I have a basic question about developing my current solution.

In the past, when I wanted to fix something (e.g., I wanted to add a new script), I just logged into the primary computer and edited the solution directly. Now that my solution is running on a server, what is the best way to develop or edit it? I noticed that I can still remote in and edit (e.g., create fields, run scripts, change layouts), but I thought I read somewhere that editing a file over an internet connection is a bad idea.

Or, should I just be shutting down my server so no new data is being entered and then pull the file to a regular version of filemaker for developing?

Edited January 9, 200916 yr by Guest

I'm sure you'll hear a lot of opinions about this. Some will swear that you should never touch a production system, and take it down for any schema changes. Others, (like me), often edit production systems while they're in use.

I would think that minor changes are OK (she says waiting for the roar). (Backups before, of course). Any major changes, I would do to a copy, and redo in production when no one is "in." Or, import/export and post new structure.