Data Separation Model Best Practices
I am finishing up my multi-user app in a single file model. I'll soon be ready to start the data separation process. I would love some input on issues and best practices others have experienced. Here are a few things I've gleaned from the Forum:
1) As long as the user security information is kept in sync, users should only have to logon once to access both files
2) $$ global VARIABLES do not cross the file boundaries. I should convert all of them to global fields to be safe. True?
3) To separate the code & data, I make 2 copies of the file then change the data source in the relationships graph then clean up
Question: Is there a way to make the data source dynamic/selectable? I'd like to be able to use different data sources for different clients.
Question: Are there best practices around where the relationships are stored (code or data files)? Performance issues with either?
Question: Do I have to do this all over again when I move everything to a server-based model?
Any other cautions or best practices you'd care to share?