Just to clarify things a little:
Access 2002 and Microsoft.Jet.OLEDB.4.0 both are accessing the JET, but with different methods.
Access 2002 uses DAO to work with JET and allows Access SQL syntax in queries.
Microsoft.Jet.OLEDB.4.0 is an OLEDB "open" driver that talks to JET ans requires ANSI SQL syntax not Access SQL. The ideas is that you can write one SQL statement that can be used by any backend database but just changing the OLEDB "driver".
Your error probably not from JET but from the OLEDB layer.
"Hi Tech Coach"
Access Based Accounting/Business Solutions developer.