Pig Posted April 22, 2005 Share Posted April 22, 2005 I am just starting out with Filemaker Pro 7. I have a fledgling Travel Company, and I will be building our initial database, after taking a couple of courses, but I have one initial question before beginning to tinker around: is there an advantage to building several databases (i.e. separate .fp7 files) that interrelate, rather than trying to cram everything into one database with lots and lots of tables? Presumably the inter-relationships should work with either approach. I shall be building a Client database, a Tour database, and several Supplier databases (hotels, restaurants, guides etc). Supplier databases could quickly become quite complex. In the not-too-distant future, it will be a tangle of scripts and automated tasks (once I'm no longer the man building it...) Any advice or suggestions are very welcome. Thanks, The pig. Link to comment Share on other sites More sharing options...
CobaltSky Posted April 23, 2005 Share Posted April 23, 2005 Hi Trufflepig, There is no single 'best' answer to your question. Some times, a single file with all the tables in one place is a great benefit, sometimes having the tables each in its own file is useful, but many times it is best to establish two or mote files with several tables in each. There are a number of considerations that will inform the choices you make about file structure - and it would take a lot more than a forum post or two to adequately discuss them all. Suffice to say that one consideration is developer style, another is user convenience and a third is functional modelling. Code complexity and useability and security considerations are also part of the equation. My suggestion is that you feel your way in the early stages and try a few different approaches (all in one file, data in one file and interface in another, multi-table modules etc) and get a feel for what the benefits and issues are with each - as well as getting a feel for whcih may suit your style and preferences as a developer. Whilst frequently, the requirements of a given system will suggest to you the structure of the system, there is nevertheless also considerable scope for your own preferences to impact decisions on structure. Link to comment Share on other sites More sharing options...
FileMakin' Tom Posted April 23, 2005 Share Posted April 23, 2005 I am still a proponent of maintaining separate, but equal, database files (No matter what the Supreme Court says). LOL Actually, the failure of a merged database would jeopardize the data in your entire system, Whereas, separate files would provide some data protection through isolation. For that reason alone, if for no other reason, I prefer the separate module format. While I believe that it is true that replication of many scripts which are common to all modules is unnecessary in a merged solution, that problem can be handled by first building a template for your new system which includes all repetitive scripts and calcs. All in all, it is simply a matter of choice . . . but think about system crashes and then make your decision how to proceed. Be well ... Tom Link to comment Share on other sites More sharing options...
Pig Posted April 24, 2005 Author Share Posted April 24, 2005 Thankyou - that's actually terrifically helfpul, just to know that it is a matter as much of preference as of the right or wrong way to do it. I shall pootle around with both, and see what comes of it. Knowing that it's not a fundamental misunderstanding on my part of what a file is relative to a table, I can proceed. Thanks. Link to comment Share on other sites More sharing options...
Ron K Posted April 25, 2005 Share Posted April 25, 2005 One thing to consider is whether your database is password protected. If so, it is easier for your users if you put multiple tables in one database - less passwords to enter and remember. Link to comment Share on other sites More sharing options...
FileMakin' Tom Posted April 25, 2005 Share Posted April 25, 2005 Not necessarily true Ron. Each user has their own same password in each file, so upon opening, all files open to the level granted by a single password. As to re-entering, that should be part of the master template design so building one's security levels is only necessary one time Tom Link to comment Share on other sites More sharing options...
Maarten Witberg Posted April 25, 2005 Share Posted April 25, 2005 hi Trufflepig, inbetween all the banter you might find some useful information in this thread: http://www.maclane.com/ubbthreads/showflat.php?Cat=0&Number=496925&an=0&page=0#496925 the main theme is, build modules, which is make clever use of fp7's ability to integrate several tables into one file, and at the same time don't forget the advantages of multiple file solutions such as Tom pointed out. kjoe Link to comment Share on other sites More sharing options...
By Soliant Consulting,
By Soliant Consulting,
By Soliant Consulting,
Recommended Posts
Archived
This topic is now archived and is closed to further replies.