References (?) in backend database

D

Dale Fye

I've been splitting my front and backend databases for a while now, and only
recently noticed that the BE databases have a bunch of references checked
when I open the VB Editor. Is there a minimal set of references that are
necessary in the backend, or do these just "bloat" the size of the mdb?

I've got references to DAO, ADO, VBA, Access 11 Obj lib, and OLE
Automation. Is any of this really needed in the BE?

Dale
 
A

Allen Browne

If there is no code in the back end database, you don't need any references
beyond the 2 required ones (Access and VBA), so you can remove the others.

The references do not really bloat the database, none of those references
are likely to break the database when you install it onto another machine or
switch versions.

While it is not crucial in the case you describe, it is good practice to use
only the references you need. More info:
http://allenbrowne.com/ser-38.html
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Question about distributing db with runtime 2
backup of database with multiple backend data bases 5
Ghost references to deleted tables in a back end database (Access2000 XP) 5
creating an MDE file when the MDB file references another database 2
References when Access 2003 and 2007 installed on same computer 3
Do I have a compatability issue here,,, 1
Type mismatch error when setting DAO property - references anddisambiguation okay 2
Quick Recovery, reset the references, split database 9

Top