Question abt referance-files for the MVP'S *922008

[J.Alladien]

Good day to all,

While opening J.VIESCAS Housing DB I got a message for a missing ref
file"OWC10.DLL version 1.1" after unchecking it I was able to work normally
in the DB, but my question is:"When you uncheck a file like mentioned above
does it mean I will not be able to use all the features in the DB but just
let's say 90% ,or will I be able to utilize all 100% of the DB"

Cause if I think logically when a component(in this case the ref-file) is
missing in a PC, or car sometimes you can still work with these objects but
not perform that specific action where the specific component is needed,which
makes the car or PC incomplete!

Is this the case in a DB example or not!
So should I find the ref file and then check it on, or is that simply not
needed!
Viescas DB is just an example ,I mean this in General for all access Dbases!

Thanks in advance for the explanation

 

[Klatuu]

Different actions within an Access database require different libraries
(references).
In some cases, Access can discerne which library is required, even if it is
not linked.

For example, you can work with the Excel object model without having a
reference set to the Excel Object Model library:

Set xlapp = CreateObjec("excel.application")

works whether you have a reference established in VBA or not. That is
because Access knows an Excel.Application needs the library and will find it
and use it. If it doesn't exist, you of course will get an error.

In other cases, where there are properties and methods with the same name
between libraries, for example DAO and ADO share some method and property
names, but behave differently, you have to have the reference established for
it to work correctly. In this instance, if you have ADO referenced, by not
DAO, then if you use:

Dim dbf As Database
dim rst As Recordset

Set dbf = Currentdb
Set rst = dbf.OpenRecordset....

Then it wil use the ADO version, but if you used
Dim dbf as DAO.Database
Dim rst As DAO.Recordset

It would cause errors.

And, in a case where the reference was not established and the library was
for an external product, particularly a none Microsoft product, it would
likely fail and not work at all.