What is he talking about? Microsoft Access doesn’t having schema, does it?!
No, and that’s the point!
I recently came across the following discussion on UtterAccess
Object Naming Convention
I want to be able to create multiple databases from a master. My master now has about 15,000 objects. I have tried to do this in two ways: 1) move individual tables/forms/reports into a new database, and 2) delete objects from the master database...
in which MadPiet’s comment regarding Microsoft Access lacking schemas got me thinking a little.
For larger projects, schemas can be very beneficial for organizing and grouping database objects (amongst other things). So instead of having one listing of all the objects mixed together, they are (or at least, can be) sub-divided and grouped by ‘subject’. So in a corporate database, perhaps we would have groupings like:
So what can be done in Access then to facilitate things? How can we make working in larger projects a little more bearable when we’re dealing with 100s or even 1000s of objects?
Continue reading →