Design separate files database for simpler hosted sync?
I am a retailer, I have been using a filemaker database solution for 3 years which has been working like a charm as a retail POS, and I am impressed by its potential, only limited by my lack of time to work on it and make it better at my amateur level. Now I would like to expand and allow the database to be deployed and to sync to different devices through a hosted server service (e.g. world cloud?).
here is my question:
I have read warnings in the Filemaker sync Guide that syncing can be complex to implement. So I would prefer to optimize/simplify current database design and maybe separate the tables into different files such as products, invoices, POs, Customers, LineItems etc. Syncing separate files containing flat tables mostly.
Problem is, there are several tables and join-tables in a database... That makes many filemaker files. I have read that only a limited number of files are allowed to be opened simultaneously. But isn't it easier and more cautious to design a hosted database system as different separate files? If not, will syncing become more complex to implement through multiple linked tables? And when data is corrupted will it make it harder to solve problems? Will crossed-linked relationships and lookup data / Summary calculations become slower through such a set-up?
Would you recommend that I get *professional help* ? (I had to write this ;-)