VBA Error 3075 with DateAdd function

  • Thread starter Thread starter dw
  • Start date Start date
D

dw

We're having some issues with a piece of VBA code that works fine on some
machines but breaks on others; we updated our MDAC on the development
machine to 2.8 and now we get this error on some user machines (where it
worked before); btw, we also updated their machines to 2.8,

Microsoft Visual Basic
Run-time error '3075'
Function is not available in expressions in query
'((({tblApplicationData].[dtmUploadDate]) Between Date () And
DateAdd("d",1,Date())))'.

Any help is appreciated. Thanks in advance.
 
Anytime you have a situation where an application works on one machine but
not on another (or that used to work, and suddenly stops working), the first
thing to suspect is a problem with the References.

This can be caused by differences in either the location or file version of
certain files between the machine where the application was developed, and
where it's being run (or the file missing completely from the target
machine). Such differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). Select Tools | References from the menu bar. Examine
all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)

For far more than you could ever want to know about this problem, check out
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html
 
Thank you, Douglas. That did the trick :)

Douglas J. Steele said:
Anytime you have a situation where an application works on one machine but
not on another (or that used to work, and suddenly stops working), the first
thing to suspect is a problem with the References.

This can be caused by differences in either the location or file version of
certain files between the machine where the application was developed, and
where it's being run (or the file missing completely from the target
machine). Such differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). Select Tools | References from the menu bar. Examine
all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)

For far more than you could ever want to know about this problem, check out
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html


--
Doug Steele, Microsoft Access MVP

(No private e-mails, please)



dw said:
We're having some issues with a piece of VBA code that works fine on some
machines but breaks on others; we updated our MDAC on the development
machine to 2.8 and now we get this error on some user machines (where it
worked before); btw, we also updated their machines to 2.8,

Microsoft Visual Basic
Run-time error '3075'
Function is not available in expressions in query
'((({tblApplicationData].[dtmUploadDate]) Between Date () And
DateAdd("d",1,Date())))'.

Any help is appreciated. Thanks in advance.
 
Back
Top