Type Mismatch BS

[isobadd]

In my department at work, we (53 users) have been utilizing a
replicated 2003 MSAccess customized db for 4 years. All of the kinks
have been worked out except one little niggling annoyance called "Type
Mismatch" which may occur 6 times a year among 6 different users. The
error occurs upon calling the sychronization process. In its several
examples of what constitutes 'Type Mismatch', MS Knowledge Base
relates that calling different data types inapppropriately in the same
procedure is the cause. I think this is a 'BS' response inasmuch as
if it (syncing) works consistently for 40 times in a row as designed
and expected and on the 41st time, the "Type Mismatch' error appears,
it has nothing to do with different data types since none of the data
types were changed in the procedure. We have overcome the problem by
either by 'Retrying' the Sync procedure, "Compact & Repair", or
overwriting (copying) the client backend with the design master
backend.

My question is, does anyone really know how to address the "Type
Mismatch" error?

thanks
Earl

[Gene Wirchenko]

On Tue, 7 Aug 2012 16:26:15 -0700 (PDT), isobadd
<iso...@optonline.net> wrote:

[snip]

>My question is, does anyone really know how to address the "Type
>Mismatch" error?

Sorry, no magic wand here.

I suggest that you:

1) check all execution paths through the procedure. In particular,
check ones that do not run that often. Some may be through error
conditions.

2) check for race conditions.

Sincerely,

Gene Wirchenko