Work on server files

[Chris Wood]

Can one make changes to, say, field definitions in a file that is being hosted on FM Server version while others are using the file??

Thanks in advance

Regards,

Chris

[CobaltSky]

No, not while it is being hosted. To do so (if it were possible, which it isn't) would be to court disaster, with users entering data into fields which no longer exist or selecting layouts which no longer have that name etc etc.

It is generally best to close the file to take it out of the grip of FM Server and open it (or a copy of it) directly as the sole host (ie with no clients logged in) with standard FMP or FMD to make the changes, then launch it under FM Server subsequently, to be hosted again.

[Kurt Knippel]

Well, not entirely true.

Starting with FM Server v5.0 and up you can make field changes to a db without taking it off the server. However you do need to be the only user and it will kick everyone else out of that particular DB until you are done.

[Chris Wood]

Thanks for these two replies. I fully understand your comments about the potential disaster of changing the structure of a file while others are using it. Making the file single user for the duration of making the change would be the answer.

The reason I asked in the first place, was that I have a colleague who runs a system of multiple (25) related files that are in constant use, so he can never get into them to make changes, which are frequently required. At present he has to work after hours when everyone has gone home!!

Thanks for your help.

Chris

[IdealData]

I am in exactly the position as your colleague. A few more files, but basically the same problem.

If I'm doing a quick fix, like adding a new field, then I'll do it with the files "live", having taken control of the file.

Anything beyond this is rigorously tested on a new "development" version. I transplant the data with import/export and host up the new files.

I'm only allowing myself a lunch period to do this, so it also helps to cut down the developments into smaller pieces, as I can only implement the changes with 1 hour of data transfer time.

Get your colleague to "trade" with the users that he could do the changes provided he can do lunch updates - or stick in for a juicy pay rise for the over time !

[Anatoli]

I do regular work on live systems over the distance of 6000 miles without problems on layouts and scripts.

Only the addition of fields requires kicking everybody else from server, and that can be arranged -- it only take couple of minutes.

[dvh71]

I have a quick question, as I have limited experience.

You make your changes in a dev/qa instance of your system (multiple files). You test. Then you truncate the dev/qa instance data, import data from the live system (import data on each file, that is), then move the dev/qa files to the production instance?

Have you built a truncate and import script (presumably a master in one file to control the whole process, and individual imports in each file) to handle the repetitive task using ScriptMaker?

Thanks for your insight...

doug.

[Kurt Knippel]

One could do this, if you find yourself doing this often enough, it is certainly worth investing in developing it.

Do it all manually the first couple of times (and document what you did), so that you know the process works. Then you can build scripts to mimic this process.