Access has 2 parts. It has the interface that you use to access your data, create and view forms, create and view reports, macros, vba code, etc.
But it also has the Jet database engine.
Jet uses .mdb files to store things, and it will store a vast array of things. That's why Access can use it to store forms, macros, reports, etc.
Jet also has a relational database management set of core funtions for doing things like maintaining relational integrity and so on.
When you use VB
with Jet to handle data, the file type is .mdb.
So if you write a VB
app using Jet, it will create “Access” files (though without forms, reports, and so on; just data, relationships, indices—data-related things).
If you wanted to, you could
write an app that uses a specialized type of chart, and stores them in an .MDB, having something like Access' database window to show the names of those stored charts in the mdb. It could look like Access, but be targeted at a special use.
So “Access files” are not necessarily associated with Access, though they can later be opened by Access.
Access “holds your hand” far more then VB
, giving you both safety and restricted capabilities...