Separate Interface and data files

[dgreco]

In the November issue of Filemker Pro Advisor, Dick Honig writes how to separate your data from the interface file. I have a keen interest in doing this, because everytime I make changes to my program, I have to go through a rigorous process of moving data to install the new version to about 10 users.

Can anyone share their experience or know of similar articles? I like to learn more about this and Dick's article was NOT to user friendly.

Thanks

[CaelC]

I didn't read the article but it seems to me you can accomplish something along these lines by using an interface DB to view all of your records in the DBs storing information.

So you would use your interface DB to design your look and feel and interactive elements but all the fields you are working with in there are displayed relationally from other DBs or through portals. It's sort of like doing a preferences DB that affects the user preference settings for an entire DB system from one file except in this case you are using a dedicated DB for interface to control the storage DBs by setting up a set of relationships to them.

Hope this helps a little.

[Anatoli]

It is very good technique for remote location with slow connection.

Everything is done through relations.

[agraham999]

I've done this...and a few different ways. When I build out a db like this I build the interface first and test the records within it...so I know that it works...then I create clones of the Interface files...strip the interface...and built the relationships. Now depending on how much speed you need...if the interface won't change...put it on each users computer. If it will...you could put the interface on one server and the data on another.

By building the interface first...and then cloning it...it cuts down on some of the work (in my opinion).