Hi Tony,
okay.......
I take it from all the "TRIM's"
that you are dealing with one or
more ODBC tables?
If so, what kind of ODBC and
which table(s)?
And if so, is it possible to create a "View"
in the ODBC db so you do not have to
use VB functions on the fields..plus maybe
the view will return only the fields you want?
And maybe there is some setting in DNS?
Are these heterogeneous Joins?
(one or more Access tables joining
one or more ODBC tables)
My limited experience with ODBC dbs
(other than SQL Server) has lead to my
feeling that it is always best to get what
I want from the db into an Access table
(no heterogeneous joins, no VB functions),
then "do something."
For example, if only table "customer" is ODBC
linked table, I probably would create a table in
Access to store what I want to pull from
"customer" with an append query, "massage it,"
then use that temp table in your query below.
I'm reasonably sure that you won't get
this behavior with Access-only tables
(I tested in Access2000 and Access2002).
I even linked to a view in SQL Server 2000
and did not get this behavior (but I did not
use any VB functions, nor attempt to include
Access tables in the query).
Also, I forgot to ask which field you are
deleting. Is the SQL you gave, the one before
the delete, or after you run the transfer.
Could you provide the "other one" also,
and identify which is which?
Also, just to make sure, have you updated
Jet 4.0 to SP8? I doubt this will help, but...
I work in a Win2000pro/Access200x world,
and just went to Windows Update and installed
SP8 from "non-critical" updates.
As far as MDAC, at
http://msdn.microsoft.com/library/default.asp?url=/downloads/list/dataaccess.asp
there is a link to "Component Checker" tool
which checks up to 2.7 (not 2.8?).
I'm not saying MDAC has anything to do
with your dilemna, and their warning about
testing newer versions in a test environment
is worth heeding!
Sorry if not much "exact help."
Gary Walter