No. You are using the object model to write the code that will open Access
itself and run an Access macro within Access.
Gotta have the Access engine to do that. Same thing if you wanted to run an
Access report: you'd need the Access engine. The object model contains no
app-like capabilities, just simply provides you the means to write code that
will manipulate the app.
Of course, data can be retrieved without having Access itself using the
Access, DAO, ADO, etc. object models. Queries or other SQL can be retrieved
and *possibly* even run without having Access open. One gotcha would be if
any Access-specific or user-defined functions are used in queries, you'd
probably need to run the queries in Access or be prepared to make
substitutions. An example of this is NZ() (Null to zero). That's an Access
function, not a VB function, so if VB (or Jet) encounters it without Access
open to provide interpretation, you're going to get an "undefined function"
error.
HTH,