In fact it is worse in the query below it is the Cstr$  that causes the
problem

INSERT INTO JapanImpByMonth ( YearMM, Country, HS, Quantity, Yen, USD,
[Month] )
SELECT [Year]*100+1 AS Expr3, qJapanImportKate.CountryName,
qJapanImportKate.HS, qJapanImportKate.[Quantity2-Jan],
qJapanImportKate.[Value-Jan], [Value-Jan]*0.5 AS Expr1,
'Jan-' & Right$(Cstr$([Year]),2) AS Expr2
FROM qJapanImportKate;

DAO  3.6 exists in Access 2000, 2002 and 2003. It's not selected by default
in Access 2000 or 2002, but it's still there, and can be selected.

Regarding your specific problem with CStr, on the machine(s) where it's not
working, open any code module. 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)

Just so you know, CStr is actually contained in the VBA library, but it's
actually unlikely that it's the VBA library that's the specific reference
that's failing. References are like apples: one bad one spoils the whole
bunch. Since the VBA library is the last one Access checks, any of the other
references being Missing will cause problems with the VBA reference.

BTW, you're dealing with VBA code, not macros. Your post would have been
more appropriately made to microsoft.public.modulescoding, or
microsoft.public.modulesdaovba.