I would suggest you have a "session" table that is a join table of contacts and "service" table. The service table assumes there is more than one service or process you provide.
The session table can store the percent complete as well as the settings used for that session, in case you decided to make a change from the base settings for the contact.
To get this on the contact card just add a portal with scrolling that shows the things you want to see.
It sounds to me that you really need to clarify your data structure. At the very least, you should be separating client data from session data. To do this you would have: (1) a Client table in which you store personal and contact details—and each client record would have a unique clientID field which you would use to build relationships; and (2) a Session table in which you would store session details—in addition to having a unique sessionID field, each record would also have a clientID_FK field in which to post the clientID of the client who is the subject of that session.
Once you have that structure organised you can have a portal to show all the sessions associated with that client—this would be what you have called a spreadsheet. A portal isn't a spreadsheet but in fact a means of displaying related records from another table in the database.
Thank you both for replying.
I have already split the session data into a second DB (second FM data base/table/file). I simply have a link from that client card to the second file for each client. Thus the to many files issue.
If I'm understanding you two correctly the idea is to have two DB. One for clients and one for session data. Using a unique client ID to keep each client's data linked but separated from other client's data in the same DB? Then use a portal to the services DB to show the client's data on there client card. I have not worked with Portals yet. Can I uses the Portal connection to filter the data so only the unique ID data shows on each client card. Seems like I should be able to that. This seams like a good idea, I'll give it a try. If this works I need to find a way to script the creation of the new client and the corresponding records in the services DB. Hmmmm
Thank I'll give this a try and let you know how it comes out.
First, it is not necessary to create two separate files. It is much better to have a single file which contains two tables.
Second, a portal is like a window that allows you to see related records from another table. If you set the relationship to Allow creation of related records, it can also be used for data entry to create records in the related table that are automatically related to the parent record.
The attached demo file should give you the basic idea.
You can have many tables in one database file. Using the Contacts starter, in File>Manage>Database you should end up with something like this:
The "=" between the Contacts table and the Sessions table is called a relationship. Double click the "=" to edit the relationship.
Here you will need to check Allow creation of records via relationship.
Then you add a portal.
Please note the settings. This will give you a a scrolling window on the layout with that contacts related information.
The relationship does the filtering and only shows the data related to that specific client. To add a new entry you can do it directly in the portal.
You all are great, Thanks for the help. I'm going to dig into all this and see what I can come up with.
I'll let you two know where I end up.
Just wonted to give and update. I have been getting lost in the cration of the DB but I'm figguring it out. Ya learning curve. But hay at lest I'm learning.
I'll keep you all posted.
1 of 1 people found this helpful
Yes. Wrapping your head around the basics if you are not familiar can be tough, but suddenly it will make sense.
1 of 1 people found this helpful
I have had to put my project on hold till I get a copy of FMP to continue working with. My trial has expired. Just updating my post.