I'm working on converting a project from Access to FM6. On Access, I have a file that stores all the code (Forms(Layouts), Reports, Tables(DataBases), Macros, VB, etc) and another file that stores all the data. The Tables(DataBases) in the main file are "linked"(they point) to the data file, so whenever I need to make changes to the Forms(Layouts) I don't have to interrupt work on the data file. I make my modifications to the main file and then replace the main file in my customer's host with the newly updated main file, all without affecting the work being done on the data file.

How can I accomplish the same effect with FM6?

This is one of the drawbacks of using FileMaker. You can develop things fairly quickly, but it is a problem to update existing customer files.

If you build the proper import scripts into the new files (and hopefully one first critical step in the old files, Find All Records), then it is possible to do this fairly easily.

It is a bit scary the first time you do it, but after doing it a few times, you see that it works; and makes fewer mistakes than you do.

The main steps to use are a scripted import, and this combo:

Set Next Serial Value [

RE: But no, you can't just drop the new file(s) in place and go.

Yes you can. I am doing just that. I saw at 2002 DevCon 2 nice ladies, which are programming in FM just with "Code" and data completely separated.

But it is *lot* of work. Relations and mostly portals must drive everything.

I guess you can have something like 90% separation between data and solution.

In my case I've started doing the separated way for remote location (production) and slow connectivity to the Main Office with FM server.

This way only data are traveling and the speed is much better, than on traditional FM database.