B
Brad Pears
In my Access 2000 application I have many dim statments throughout the code
to define a variable called "RS" which is a DAO recordset object.
However, anytime I try to dim it as such, the "set RS =
currentdb.openrecordset(strSQL)" command fails. So, I have resorted to
dimming it as an object and that works just fine... i.e..
"dim RS as Object" INSTEAD OF "dim RS as DAO.Recordset"
Is there any problme with doing this? Will I be incurring additional
overhead as now it has to figure out what type of an object RS actually is
at runtime??
Why may my "dim as dao.recordset" not be working?? I have a reference set
to the DAO 3.6 object library...
Thanks, Brad
to define a variable called "RS" which is a DAO recordset object.
However, anytime I try to dim it as such, the "set RS =
currentdb.openrecordset(strSQL)" command fails. So, I have resorted to
dimming it as an object and that works just fine... i.e..
"dim RS as Object" INSTEAD OF "dim RS as DAO.Recordset"
Is there any problme with doing this? Will I be incurring additional
overhead as now it has to figure out what type of an object RS actually is
at runtime??
Why may my "dim as dao.recordset" not be working?? I have a reference set
to the DAO 3.6 object library...
Thanks, Brad