Changing a copy of a layout and resaving to original without losing new data?

[aagee]

I travel alot and I have a database in progress and my employees are wanting to start entering data. I still have a lot of work to do on the reports and different scripts for certain functions required but all fields are there to input the raw data. I need to work on the complete database and save the work that I have completed when I get back home to the database without disturbing the actual data. How do I do this. I hope that you understand what I am asking. I am new to FM so I have limited knowledge to the terminology of this program.

Edited February 20, 2008 by Guest

[mr_vodka]

you may want to look into the seperation model. If not, you could work on your copy and when you are ready you can import the data that has been etnered into the updated one.

[David Jondreau]

Layouts and data are separate entities, so you don't need to worry about losing your data. But if you are referencing Layouts in your scripts, you should reference by calculation by name.

[Fenton]

aagee, what you are proposing is possible, but dangerous. You must understand a fair amount about FileMaker to do this safely. Basically you build your copy of the database, then, when you're done with a "version," you empty it all out, then Import their current data, resetting all serial IDs where needed (important!).

This is not something to be done casually or often, or without knowledge of the ramifications. That is one reason mr_vodka suggested the Separation Model. It greatly eases the burdens, but adds something to the learning curve itself.

What kind of access do you have to the "live" files? It may be possible to do some work on them, though you need to be a bit careful.

If not, how often do you envision swapping your development files with the live ones?

Do you have FileMaker Server hosting the files? On its own machine? If not, I wouldn't even consider working on the hosted files, too dangerous; heck, it's even a little dangerous just for data entry -|

Edited February 20, 2008 by Guest

[David Jondreau]

I misunderstood what the OP was doing.

I think you'll need to learn robust importing techniques to do what you want.

[Fenton]

Yes, I first thought that too, as the subject line just says "copy a layout". But this goes much further than that. Upon reading the original post again, I see that he's often on the road. So my advice re: working on the live files is pretty much out of the question (for structural changes anyway).

The phrase "save the work that I have completed when I get back home to the database without disturbing the actual data" is actually backwards. You build the structure of the files on your independent copy. You then Import the real data into an empty (could be Clone) copy of your newer file; not the other way around. It's possible (though it requires care and feeding) to Import data. It is not possible to "save structure onto/into existing files,"* not as a 1-shot operation anyway (you can copy/paste/import layouts, fields, scripts, but not all of these at once as a single structure, and not relationships on the Relationship Graph at all).

*As mr_vodka says, it is possible to swap in a new "interface" file, if you've used the Separation of Data Method. In your situation I would look hard at that possibility.