Create a self relationship on the id key and then give the occurance a name related to the database. Example ("Appointment Count") You will need a relationship for each portal you want to count records. Then you need a calculation field with the following calculation : Count(Appointment Count::Appointment Date) and under storage options check the box do not store but recalculated as needed. Then place the field on your tab and bring the field to the front,
Great.. thanks... two questions:
1) Why would this new calc field be showing a "?" on some records and then display the correct number on others?
2) Also, some of my users may be accessing this solution on slow networks (like I am right now) and I notice that the "sorting" on each record load is taking some time. Not too bad now, but once I add this feature to all 4 tabs, it may be too slow to keep this feature.
Solved my first problem with the "?"... I had the field set too small...
It's hard to diagnose network issue without any more information. When it comes to speed on networks it boils down to ram, and harddisk speed. On both ends. (Server and Client). There are other items that can change the speed, such as the number of user, but the basic starting point is ram and harddisk speed. I understand that fmp 12 is slower than previous versions of fm.
You may have to move the record count from the tabs and place inside the tab above the portal so it only recalculates when you click the tab to view the portal. Not as informative because the user can't see all counts at one time but you still have the information availiable for viewing.