Should forms, reports, macros, modules ever be in the back end of a split Access database?
Posted on 2011-04-26
I have acquired an Access 2007 database. It is split into a front end and a back end. The back end contains forms, queries, reports, macros, and modules. Most of these are the same as what is in the front end and some are unique only to the back end.
I have never seen a database which stores forms, etc, in the back end. My question is this:
Is there ever a good reason to set up a database like this? The back end forms import data from
Excel. I have always put this functionality in the front end.
Did this developer misunderstand the meaning of front end/back end or is there some logical reason for setting up a split database with forms, reports, macros, etc in both the front end and back end.