I am considering using ms_SQL for a full backend to my Filemaker frondend.
My main reasons are:
1 - so I can base layouts on advanced queries/views in the sql DB
My reason is that I believe this would be much faster than using filemaker and omiting/finding records as the layout loads, especially as I could return only the columns & rows i need at the backend.
2 - With the data in msSQL its easy for other applications to access that data as its a more common standard.
So I was hoping for opinions on these 2 points and maybe some potential pitfalls "down the line".
for example I al already seeing that the relationship graph & instances of tables can be a little unpredictable when connection to SQL.
e.g I have a table occurance that linked to a back end SQL table but filemaker refused to see any records no matter what i did. So, I had to create another table instance which worked fine (to the exact same table), problem was I had to remap every layout and field on that layout to the new table instance.
Im just afraid of causing too much hassle for myself.
It would be easier to just use filemaker and accept points 1 & 2 as they are?
Any experience would be appreciated.