J
Jim Shaw
BlankI have "compact on close" general option set for both my front and
back-end dbs.
I do a lot of table add, delete, change activity, from the front-end, on the
back-end db.
The front-end tables are "linked" to the back-end db, therefore my front end
VBA code does not explicitly "open" the back-end, nor does it "close" the
back end.
Will the back-end db be compacted when I close the front-end db via the
"linking" mechanism, or must I use, in the front-end, the compact method in
the DbEngine object to get the back-end db compacted? If so, that raises
the issue of the back-end being compacted while the front-end is still open;
I hope the locking mechanisms take care of that?
Thanks
Jim
back-end dbs.
I do a lot of table add, delete, change activity, from the front-end, on the
back-end db.
The front-end tables are "linked" to the back-end db, therefore my front end
VBA code does not explicitly "open" the back-end, nor does it "close" the
back end.
Will the back-end db be compacted when I close the front-end db via the
"linking" mechanism, or must I use, in the front-end, the compact method in
the DbEngine object to get the back-end db compacted? If so, that raises
the issue of the back-end being compacted while the front-end is still open;
I hope the locking mechanisms take care of that?
Thanks
Jim