Thank You - Solved the Problem. Suggest you add this to your next update to
Article ID # 31881 for us amateurs.
Glad to hear it. Thanks for the feedback. There's a place at the bottom of
the article where you can make the suggestion.

Signature
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
| Thank You - Solved the Problem. Suggest you add this to your next update to
| Article ID # 31881 for us amateurs.
Just a comment. It's not quite as simple as that.
If you're not going to be using ADO, uncheck the reference to Microsoft
ActiveX Data Objects 2.1 Library when you add the reference to DAO.
If you have both references, you'll find that you'll need to "disambiguate"
certain declarations, because objects with the same names exist in the 2
models. For example, to ensure that you get a DAO recordset, you'll need to
use Dim rsCurr as DAO.Recordset (to guarantee an ADO recordset, you'd use
Dim rsCurr As ADODB.Recordset)
The list of objects with the same names in the 2 models is Connection,
Error, Errors, Field, Fields, Parameter, Parameters, Property, Properties
and Recordset

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
> Thank You - Solved the Problem. Suggest you add this to your next update
> to
[quoted text clipped - 21 lines]
>> |
>> | Can anyone help me as to what is incorrect in VB