Search the Community
Showing results for tags 'database design'.
Found 3 results
Dear all, We have developed an internal Filemaker solution for our shipping company for the past two years. It has evolved to become the very heart of our business. Now the other offices around the world want to share our joy! Today we run it only in our New York office with twelve users. We have create about 10k records per month and have about 200k records in the database spred over three four main tables. Worldwide we would need to be able to scale to 100k records per month and 2M+ records in the database and 100 users from 10 countries. My first question is could filemaker support this from one server? Since management love world wide consolidates reporting there are many obvious advantages to hosting one main server for all countries. Do you have experience from this? Secondly, I need convert the one-country solution we have today, into multi office, multi language. If I do host everything on one server, in one database, what do you suggest for optimal performance and security if it is important that users only see their country specific information? I am already today using the login name in a relationship to filter out data to be seen by each particular user, i.e. my customers, my tasks etc. Should I try to apply the same logic to transactions, adding a "HomeCountry" field and then create a relationship which using a global variable "CurrentHomeCountry" set at login to filter information pertaining to your country? Any input is greatly appreciated!
Ah, okay that makes sense! Thanks so much for all your advice. Okay, my next issue is as follows.... So I have a layout for 'Tracking Sessions' which contains details of each time someone went out to find a particular individual/group of cheetahs. Within this layout, I have a Tab that contains different portals to different tables of information that could be (but not always) collected during a specific tracking session (e.g. kills found, supplemental feeding, and 'Tracking Notes'). Now, because of the Join table how can I set these portals up to allow for record creation in these child tables while also creating the necessary records for the join tables? I've included a screenshot of the layout. Everything under 'Kill Details' is contained within a single portal row, as there is usually only a single kill during a single tracking session (though I guess in theory there could be more than one at some point in the future). From my experience and what I've read, you can't place a portal within a portal so how do I solve this issue while maintaining the current format (or if there is a better way of doing this, I'm all ears!) I've also included an updated screenshot of my relationship table, so you can see where tracking sessions lies in relation to kills and cheetahs.
I'm working on a database to store/organise data pertaining to Radio/GPS collared cheetahs (e.g. movements, kills they've made, etc.). Within the database, my main table is 'Released Cheetahs' which contains all the information about an individual cheetah and their local ID number, which is called 'AJU#'. AJU# is the field relating 'Released Cheetahs' to the other main tables within the database (Fix Data, Kills, Tracking Sessions, Parturitions, Releases, Captures, etc.). Some of these cheetahs (and thus the records within 'Released Cheetahs') are in groups of a few individuals, which is delineated by 'Group Name'. My problem is that when I make a entry into one of the other tables, let's say 'Kills' (which contains info about the prey they have successfully hunted), with my current design I would need to duplicate this record for every cheetah within the group, but I would rather be able to just list all of the cheetahs (i.e. AJU#s) within a single field of the 'Kills' table so that there is only one entry per kill. So, my question: What would be the best way of tying each kill record (single 'child' record) back to each of the cheetahs (multiple 'parent' records) it pertains to? I know I could just look at this from cheetah group rather than individual, but even though there is a group each kill record does not always pertain to each cheetah within a given group. I have tried playing around with repeating fields (e.g. using a repeating AJU# field within the Kills table) but I can't quite seem to get this to work as hoped. Any advice is most welcome! I've attached an image of my relationship graph in case that helps.