Separating layout and database

[lazyyy]

Dear all,

I have a database which I plan to separate it into two different files.

One files for all layouts and the other files is for all the tables.

After that I will do the kiosk mode for the layout files.

Is there a simple way of doing it while i still get to keep my scripts working properly?

Thanks

[Inky Phil]

I don't think there is a simple answer to this question.

I suggest you look up 'seperation model' I think there is even a forum dedicated to it here on this site - under Brain Food.

You should find plenty of food for thought there

Phil

[T-Square]

It is not clear why you think that having your files separated will affect your scripts' functionality; if you build a script on a separated structure, it will work just fine.

I suspect that you're working with a pre-existing database that you're looking to split. In that case, you have to rebuild your relationship graph to use the data tables in the linked datafile.

If possible, start out the design process by separating your files, since modifying your scripts after the fact is FAR more complex than getting the links set up to begin.

If in fact you ARE migrating an existing solution, I'd recommend biting the bullet now, getting your structure in place, and moving forward from there. It will only get more difficult as time goes by.

As Phil notes, the Separation forum addresses many of these issues in depth, including the sticky question of migrating into this format.

David