I am starting to create an MSAccess database, I have no Access experience – my previous experience is with MySQL and Oracle. Initially I had some difficulty coming to terms with the fact that MSAccess usually stores both the front end application and the Jet Engine database in the same file. It’s different from what I’m used to. Plus the database will be shared over a network, and it just makes more sense to split the application from the data.
After some reading, I see that it is possible to store data in one file, and then link to the application elements in another file. Every article I’ve come across for this deals with splitting the database into two parts, after the database has already been made, and never discusses creating split database applications from the start. Is it because that would be a bad idea? I can’t really imagine why, except that I’ve noticed that Access does not let me keep two database files open at the same time (it automatically closes one). So I am foreseeing a need to constantly to open and re-open files if I go down that route.
There is one practical reason why you might want to start with a single database. If you start with a front and back end file, you’ll have to create tables in one database, then set up the link for each table manually.
This is not a big deal, but if you’re just starting the system, you can save some busywork by developing the pilot system in one file, then splitting it. My assumption is you’ll probably be making a lot of changes to the data structure at the outset; your work will go smoother if you’re working in one file.
It is definitely a good idea to split the database before you deploy it to production. I’m not sure why you’re having problems opening 2 Access files at once; this is not a restriction of Access.