ms access - Should references to DAO be set on every client machine? -

ms access - Should references to DAO be set on every client machine? -

i have access db front-ends on client machines , back-end on server.

i never needed utilize references dao, time have utilize concatrelated module work. have deploy updated front-ends, i'm not sure if reference set on machine work on other machines.

i don't have experience , don't know if references have set on each machine (many of them utilize different versions of access: 2003, 2007, 2010) or info straight front-end.

if have set everywhere, have find solution without dao.

thank you!

i work in environment users on xp , on win7. utilize access 2003 utilize access 2010. when deploying databases, broken references mutual problem.

my workaround declare objects using createobject instead of via references.

the next illustration utilize when have ado in references.

dim rst new adodb.recordset

the next illustration how can utilize ado recordset without reference:

dim rst object set rst = createobject("adodb.recordset")

this lets operating scheme determine right library. code completion won't work method - may easier write code, test it, , createobject trick.

ms-access reference dao frontend