Good day!
This past weekend I was reading up on normalization of tables, recommended to me by Colin (isladogs) in my first thread here on the forums.
It was very insightful (thank you for that, Colin!), and in one of the articles that I read, splitting databases was mentioned, into front-end and back-end, for the following purposes:
1. Allowing several users to share over a network.
2. Performance improvement.
3. File corruption prevention.
I found this very interesting, and reading further on this topic, I understood the following general rules:
a. all tables should all be on the back-end files.
b. all forms and reports on the front-end files.
But I read conflicting information as to where the queries should be stored > some sources state they should be on the back-end, while others state they should be on the front-end.
May I ask forum users, who use split databases, what your insights / experiences / suggestions are on this topic? Some first questions that come to mind are:
i. How are the files/folders organized?
ii. Is it possible, recommended or not recommended to have multiple back-end files for one front-end?iv. How are queries stored and structured (in front-end, back-end, or both)? Any cases where I should consider queries being stored anywhere other than the front-end?
iii. Should there be only one front-end file? Any cases where I should consider multiple front-end files?
v. I understand that the front-end file will link to tables from the back-end. Any cases where I should consider having back-end files linking to other back-end files?
Thank you in advance!