Should forms, reports, macros, modules ever be in the back end of a split Access database?

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.

Who is Participating?
Rey Obrero (Capricorn1)Connect With a Mentor Commented:
he probably forgot to remove the objects aside from the tables in the BE.

see this link, for reasons why you have to split an application
peter57rConnect With a Mentor Commented:
I suspect that it was just a mis-op by the developer.
Possibly they created the front-end by importing objects from the complete application file and then used the original file as the backend.

The backend might hold objects required for maintenance and support but in terms of 'live' objects, generally I would only expect to find  tables in the backend.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.