Setting Object References in Access Modules by using VBA Code

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

One of the issues that seems to arise with Access is a migration from an older environment (like Windows 98 or 2000) to XP. When you create the new database in XP, the module code does not compile. This is because some of the methods that were valid in the old environment are not necessarily recognized in the the new. This can be alleviated by opening up any module created in the Design mode and then clicking Tools and then references and setting certain library references by checking off the items needed to recognize "backward compatibility".

My question is, is there a way to set these flags on automatically by writing a Visual Basic Access function and then executing it when the database launches ?
 
My question is, is there a way to set these flags on automatically by
writing a Visual Basic Access function and then executing it when the
database launches ?
Click to expand...

Rumour has it that Access 2003 sets the default back to DAO, but I don't
know if it's true or not. Would be nice if it was a program default, but
there you go...


Tim F
 
Tim Ferguson said:
Rumour has it that Access 2003 sets the default back to DAO, but I don't
know if it's true or not. Would be nice if it was a program default, but
there you go...
Click to expand...

DAO is there, but I'm not sure it's the default. Both ADO and DAO are
present, but I'm not sure which is higher in the sequence, as I haven't
installed 2003 yet.
 
You can use the References collection's AddFromFile or AddFromGUID methods
to add a reference.

You only need to do it once, as the references are stored in the MDB file
itself, not in Access.

--
Doug Steele, Microsoft Access MVP

(No private e-mails, please)



Dave Reynolds said:
One of the issues that seems to arise with Access is a migration from an
Click to expand...
older environment (like Windows 98 or 2000) to XP. When you create the new
database in XP, the module code does not compile. This is because some of
the methods that were valid in the old environment are not necessarily
recognized in the the new. This can be alleviated by opening up any module
created in the Design mode and then clicking Tools and then references and
setting certain library references by checking off the items needed to
recognize "backward compatibility".
My question is, is there a way to set these flags on automatically by
Click to expand...
writing a Visual Basic Access function and then executing it when the
database launches ?
 
Stupid typo: that should be "program option"...
DAO is there, but I'm not sure it's the default. Both ADO and DAO are
present, but I'm not sure which is higher in the sequence, as I haven't
installed 2003 yet.
Click to expand...

All the best


Tim F
 
Back
Top