iammontoya

Thank you for your reply. Man, I really hope that is wrong, because paying 349 dollars just to connect a date with the calendar is crazy steep. On top of that, It's gong to force me to either ask my customer to use two calendar apps (which also means that I would have to build some super robust internal calendar on FileMaker), or I'll have to move on to something else entirely. That is bizarre that FM did not include a way to do that. Dont you think?

I didnt really follow your example very well, but the rule of thumb is that all your tables should simply have a one-to-many relationship. Based on what I gathered from your example, I would say you need an extra table to avoid having a many-to-many relationships in your database design.

I have a simple app that is tracking sessions with clients. 1 client, multiple sessions. On another layout page, we set up the next appointment. I need that appointment to go into the IOS calendar (so alarms, alerts, etc... will work). Any thoughts? Thanks!