Suggestions:
1. Use "Me." before each reference, so the compiler will notify you if you
have a name wrong. Also, bracket each part of the expression. So:
If (Me.[A/R1] = "Quarterly")
And (Me.[QtrDate1] <> Me.[QtrDueDate1])
And (Me.[QtrDate1] <> Me.[QtrDueDate2])
And (Me.[QtrDate1] <> Me.[QtrDueDate3])
And (Me.[QtrDate1] <> Me.[QtrDueDate4]) Then
2. I can't tell from the way the newsgroup broke up your post whether the
assignment is on a separate line. In any case, make sure it is:
Me.ARAgingRecd1 = "n/a"
3. When you open your table in design view, is [A/R1] a Text field?
Comparing it to the string could give the error if it is actually a number
or date.
4. Is ARAgingRecd1 a text field? Same issue.
5. Is QtrDate1 unbound? If so, set its Format property so it is the same
data type as QtrDueDate1 and the others. For example, if they are date/time,
set the Format property of the unbound text box to General Date. Also, don't
programmatically assign a zero-length string to it, as that forces Access to
treat it like text: instead assign Null, e.g.:
Me.QtrDate1 = Null
not
Me.QtrDate1 = ""
6. If any of these are calculated query fields, view the query output
directly, and see if the columns left-align like text, or right-align like
number/date fields. This may give you a visual clue where the data type
mismatch is occurring.
More info in:
Calculated fields misinterpreted
at:
http://allenbrowne.com/ser-45.html
7. Since you are getting different results on different machines, you may
want to investigate what differences exist between the machines. They may
need a service pack for Office or for JET 4. Both available from:
http://support.microsoft.com/sp
If the service packs are identical, perhaps it's a difference in regional
settings (e.g. date formats.)
8. Be aware of the impact any Null value would have on your ANDs.
