DAO 3.51 vs DAO 3.6

[JPG]

I am having an issue with various PC's and the references set in my Access
DB. I am using Access 2002 and have DAO3.6 seleted as a reference but on
ertain PC's I am getting an error saying "That command is not available."
When debugging the error hits on the .edit of a recordset. What I have found
is that on the machines where I encounter this problem, the only DAO
available is the 3.6. When I manually load the 3.51.dll and select it as a
refernence instead, everything runs fine. I thought that the 3.51 was for
previous versions of Access?

 

[Douglas J Steele]

3.51 is for Access 97. Access 2000, 2002 and 2003 all use 3.6.

 

[JPG]

Thanks Doug,
Do you know why I would be getting this error, even when referencing 3.6,
only on the machines that do not have the 3.51 installed?

 

[Douglas J Steele]

What's the actual code you're using?

 

[JPG]

Here is a snippet from the beginning of this module:

Public Sub Add_System_Calculations_to_Table(strPRB, intDaysPastDue) 'module 4
With Session

Dim dteCurrentdate As Date
Dim RecSet As Recordset
Set DB = CurrentDb

dteCurrentdate = Date


SQL = "SELECT * FROM tbl_User_Transactions"
Set RecSet = DB.OpenRecordset(SQL, dbOpenDynaset)

RecSet.AddNew


RecSet.Fields("Processor").Value =
[Forms]![frm_Log_In]![txtUserID]


It is at the RecSet.AddNew that I get the following error:

Run-time Error '3320'
Function is not available in expressions in table-level validation expression.

As I mentioned earlier this runs fine on certain machines, but the ones were
I get the error are missing the DAO 3.51, which I am not referencing
originally. If I manually load this .dll and set the reference to it, it runs
fine. The problem is that this is on a network and I am unable to make this
manual change to all PC's. Additionally, I don't understand why the 3.51
works over th e3.6 in Access 2002.

Your assistance is greatly appreciated.

 

[Douglas J Steele]

You're trying to use DAO code. By default, Access 2000 and 2002 don't have a
reference set to DAO, and in Access 2003, the reference to ADO is higher in
the list, thereby giving it precedence over DAO.

Recordset happens to be an object in both the ADO and DAO models, so unless
you disambiguate, you're probably not actually getting a DAO recordset.

Try changing your declaration to

Dim RecSet As DAO.Recordset


--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

Here is a snippet from the beginning of this module:

Public Sub Add_System_Calculations_to_Table(strPRB, intDaysPastDue) 'module 4
With Session

Dim dteCurrentdate As Date
Dim RecSet As Recordset
Set DB = CurrentDb

dteCurrentdate = Date


SQL = "SELECT * FROM tbl_User_Transactions"
Set RecSet = DB.OpenRecordset(SQL, dbOpenDynaset)

RecSet.AddNew


RecSet.Fields("Processor").Value =
[Forms]![frm_Log_In]![txtUserID]


It is at the RecSet.AddNew that I get the following error:

Run-time Error '3320'
Function is not available in expressions in table-level validation expression.

As I mentioned earlier this runs fine on certain machines, but the ones were
I get the error are missing the DAO 3.51, which I am not referencing
originally. If I manually load this .dll and set the reference to it, it runs
fine. The problem is that this is on a network and I am unable to make this
manual change to all PC's. Additionally, I don't understand why the 3.51
works over th e3.6 in Access 2002.

Your assistance is greatly appreciated.

What's the actual code you're using?

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)


have
found it as
a was
for

 

[JPG]

Great Help. Thanks a million.

You're trying to use DAO code. By default, Access 2000 and 2002 don't have a
reference set to DAO, and in Access 2003, the reference to ADO is higher in
the list, thereby giving it precedence over DAO.

Recordset happens to be an object in both the ADO and DAO models, so unless
you disambiguate, you're probably not actually getting a DAO recordset.

Try changing your declaration to

Dim RecSet As DAO.Recordset


--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

Here is a snippet from the beginning of this module:

Public Sub Add_System_Calculations_to_Table(strPRB, intDaysPastDue) 'module 4
With Session

Dim dteCurrentdate As Date
Dim RecSet As Recordset
Set DB = CurrentDb

dteCurrentdate = Date


SQL = "SELECT * FROM tbl_User_Transactions"
Set RecSet = DB.OpenRecordset(SQL, dbOpenDynaset)

RecSet.AddNew


RecSet.Fields("Processor").Value =
[Forms]![frm_Log_In]![txtUserID]


It is at the RecSet.AddNew that I get the following error:

Run-time Error '3320'
Function is not available in expressions in table-level validation expression.

As I mentioned earlier this runs fine on certain machines, but the ones were
I get the error are missing the DAO 3.51, which I am not referencing
originally. If I manually load this .dll and set the reference to it, it runs
fine. The problem is that this is on a network and I am unable to make this
manual change to all PC's. Additionally, I don't understand why the 3.51
works over th e3.6 in Access 2002.

Your assistance is greatly appreciated.

What's the actual code you're using?

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)


Thanks Doug,
Do you know why I would be getting this error, even when referencing 3.6,
only on the machines that do not have the 3.51 installed?


:

I am having an issue with various PC's and the references set in my
Access
DB. I am using Access 2002 and have DAO3.6 seleted as a reference but on
ertain PC's I am getting an error saying "That command is not
available."
When debugging the error hits on the .edit of a recordset. What I have
found
is that on the machines where I encounter this problem, the only DAO
available is the 3.6. When I manually load the 3.51.dll and select it as
a
refernence instead, everything runs fine. I thought that the 3.51 was
for
previous versions of Access?

 

[shn]

I am having an issue with various PC's and the references set in my Access
DB. I am using Access 2002 and have DAO3.6 seleted as a reference but on
ertain PC's I am getting an error saying "That command is not available."
When debugging the error hits on the .edit of a recordset. What I have
found
is that on the machines where I encounter this problem, the only DAO
available is the 3.6. When I manually load the 3.51.dll and select it as a
refernence instead, everything runs fine. I thought that the 3.51 was for
previous versions of Access?