Does anyone have experience using a scheme like this? The situation is one database that is mainly concerned with creating and actually working with the data. Then there are these 'satellite' locations that run a different database that is based on the same structure and data but has different forms and methods. So the "main" (we'll call it) datafile is periodically sent to these other locations to be installed. Occasionally the satellite locations will move a datafile back to the "main".
I know some you you used to do this in the past. And now you know some of us are still doing it. It's critical that the table and field arrangement not change. I'm wondering if it's as critical with regard to things like table and field names. My understanding is these are basically labels (but the table numbers and field numbers are not). In tests I'm able to move a datafile between two structures where the names are different but the underlying structure stays the same. Just wondering if there are any other issues to be aware of with a deployment like this. And any other approaches to achieving this sort of distribution. Thanks -- Kirk Brooks San Francisco, CA ======================= ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
