I'm 100% convinced on the merits of splitting databases: I want my tables to reside on a network drive and users to access the info via a front-end which resides in their 'private' drive on the same server.
The question is how/when to split the database.
- I know that I could create the database locally (initially) and have it contain all the tables, queries, forms, etc., and then use the SPLIT TOOL to move the tables to a back-end location.
- Alternatively, I know I can create the accdb file at the server location where the tables are going to reside and then, once that's finished, create a new accdb file at the local drive and simply link to the tables in the other file on the server. I can then create all the queries and forms I need here.
Is the net result of 1 and 2 the same?