updating running databases

[Tony Hill]

Hi

I am about to implement a multi-user db on FM server 10 on Windows and I know that two things are certain:

1. I will have bugs in my coe

2: The users will want functions they had not told me about.

this means updating the system moving forward. What tools (if any) are there to aid the migration of new/updated scripts into a 'running' system.

[bcooney]

I'm not aware of any "tools". Our typical approach is to take down the production system, import its data into the new version, and then re-serve the new version.

See this thread

[LaRetta]

It also really helps if you use seperation model. Then you can usually replace the UI file (although sometimes you will have a field or two to add to the data file in support). This means no migration of the data into the new tables.

I will never go back to data and UI in same file again.

[Steven H. Blackwell]

Both Barbara and LaRetta have given you some options and suggestions. Like LaRetta, I use The Separation Model™ and have been doing so since FileMaker® Pro 7 came out.

Do be especially careful if you make schema changes on live, hosted files. If your connection drops, your files will likely sustain damage. This is less likely with FileMaker® Server 10 and FileMaker® Pro 10 than with earlier versions. But it is still a possibility.

Steven