What I see in your screenshots is what appears to be layouts from "flat files". Have you looked into the "relationshiip" capabilities of Filemaker? You should have a table just for the students and another table just for your courses offered and another table that could be called Registration which joins a specific student with a specific course. I would highly recommend that you get your hands on a copy of "Filemaker Training Series" and read over Module 3 (Data Modeling). That will give you a handle on how to set up your database so you can get the information you want with a minimum of layouts.
1 of 1 people found this helpful
Another thing that is great for forum discussions/ archives, is to have a header that summarises the query. So instead of "Very big problem...please help me", you could try 'How to calculate salary' or 'Calculate salary based on student numbers' or 'Calculate salary based on enrolments'.
Encapsulating the first question is a bit harder plus, it's often a good idea to try and keep the queries separate. How about 'How to Sort or Filter Data', or 'How to Display Filtered data'? Sometimes it's hard to come up with a good header because you don't know the correct technical term/ jargon but that's all a part of the learning curve.
All the best,
Actually I tried to summarize the question as the header, but based on my posts before, views are very less when people read the header and they aren't interested about my question. So, this time I tried to put the header as something that people has no idea what it is and they are really curious to know more about it. This time it worked, I got more than 85 views in not even 24 hours. There's even a post of mine that actually got only 21 views even though it was posted months before.
I'm really sorry if there's any of you are mad at me saying that reading this post is a waste of time.
Fair enough. (Would still strongly discourage this approach in the future tho' :-) ) And I'm sure that Mark's excellent and fast answer has been very helpful, yes?