On four references

[Ennex]

Okay, thank you to Dirk Goldgar and George Nicholson. I changed:
-- "Dim ___ As Database" to "... As DAO.Database"
-- All occurances of "As Table" to "As DAO.Recordset"
-- All occurances of ".OpenTable" to ".OpenRecordset"

The compiler issued one final ByRef error, which I fixed, and the code now
compiles and the forms fill out with no errors. So thank you for your quick
and helpful replies. How is it that this very helpful resource is free???

As they also recommended, I removed the reference to ADOX.

Now I have a question about four other references:

#1. Should I also deselect the reference to ADO:
Microsoft ActiveX Data Objects 2.8 Library (MSADO15.dll)

When I fist started looking at references, they included:

#2. OLE Automation (StdOLE2.tlb)
#3. Microsoft Visual Basic for Applications Extensibility 5.3

Should these be left in or deselected?
The code seems to complile and run fine with or without the above three
references.

#4. The references also originally included one called "utility". But after
I deselected it, it disappeared from the list and I've never seen it since.
What was that and do I want it back for any reason?

Thanks again for your help.

Regards,
Marshall Burns
www.Ennex.com

 

[Dirk Goldgar]

Okay, thank you to Dirk Goldgar and George Nicholson. I changed:
-- "Dim ___ As Database" to "... As DAO.Database"
-- All occurances of "As Table" to "As DAO.Recordset"
-- All occurances of ".OpenTable" to ".OpenRecordset"

The compiler issued one final ByRef error, which I fixed, and the
code now compiles and the forms fill out with no errors. So thank you
for your quick and helpful replies. How is it that this very helpful
resource is free???

As they also recommended, I removed the reference to ADOX.

Now I have a question about four other references:

#1. Should I also deselect the reference to ADO:
Microsoft ActiveX Data Objects 2.8 Library (MSADO15.dll)

If you aren't using ADO, and don't intend to, go ahead and deselect that
reference. For most purposes, in an MDB file you don't need ADO, and
leaving that reference out will save you from possible errors when you
declare objects of types that are defined in both the ADO and DAO
libraries. It's still a good idea to qualify the declaration of DAO
objects with "DAO.", though, just in case you later have some reason to
add the ADO reference again.

When I fist started looking at references, they included:

#2. OLE Automation (StdOLE2.tlb)
#3. Microsoft Visual Basic for Applications Extensibility 5.3

Should these be left in or deselected?
The code seems to complile and run fine with or without the above
three references.

I'd leave OLE Automation, but you probably don't need the VBA
Extensibility library.

#4. The references also originally included one called "utility". But
after I deselected it, it disappeared from the list and I've never
seen it since. What was that and do I want it back for any reason?

That reference will be created whenever you use various of the built-in
wizards. You don't have to concern yourself with it one way or the
other.

Thanks again for your help.

You're welcome.

 

[John Vinson]

The compiler issued one final ByRef error, which I fixed, and the code now
compiles and the forms fill out with no errors. So thank you for your quick
and helpful replies. How is it that this very helpful resource is free???

The people who post most of the answers receive very low (zero, to be
exact) salaries. We're all volunteers here... <g>

Join us if you like! It's a lot of fun. Start by answering the
questions you're comfortable answering, and go on from there... I warn
you, it's addictive, though!

John W. Vinson[MVP]

 

[Ennex]

Hey, guys, thanks very much! The bottom line problem was that the code was
written years ago and never updated for changes in Access. So thanks for
helping me troubleshoot the problems and get it working again.

Regards,
Marshall Burns
www.Ennex.com