Error 3464 with dCount - some computers only

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

A user of one of my applications gets the error message "Run Time
Error 3464 - Data type mismatch in criteria expression" from this line
of code:
If DCount("*", "qryDocReviewRemind") > 0 Then

The error also arises if I try to print this dcount expression in the
immediate window, on the user's computer.

The query itself runs fine, and produces a recordset with 36 records
from the current data.

If I run the same database (the same physical file - not a copy of it)
on my computer, this code (and the print in the immediate window)
works fine.

I'm at a loss here; and a search of the Access newsgroups has not
produced anything of assistance (although it has produced lots of
hits). Any suggestions would be gratefully appreciated.

TIA,

Rob

.

Relevant Pages

  • get the sql statement
    ... Data type mismatch in criteria expression. ... Protected Sub btnSave_Click(ByVal sender As Object, ...
    (microsoft.public.dotnet.framework.aspnet)
  • >255 into excel?
    ... I need to insert more than 255 chars into an excelcolumn ... "Data type mismatch in criteria expression." ... ('VAFocus - ADH','Item cannot be found in the collection corresponding to ...
    (microsoft.public.inetserver.asp.db)
  • Re: Update query
    ... > It *should* set the value to NULL if the Allow Zero Length is false. ... Data type mismatch in criteria expression. ... Those are 2 single quotes... ...
    (microsoft.public.access.queries)
  • Re: sort report by year (weird format)
    ... its okay - i get the error "data type mismatch in criteria expression" ... can i use a query?) ... Marshall Barton wrote: ...
    (microsoft.public.access.reports)
  • RE: Referencing Field names in Parameters
    ... As to your data type mismatch, I don't know why that is happening. ... need to establish the parameter value before you open the recordset. ... >> I learned about parameters when I had a case where I had 3 criteria set in a ... >> the order of the query and caused my query to go crazy, ...
    (microsoft.public.access.modulesdaovba)