I Googled around a little. Seems like the consensus was that it's something to
to with a corrupted DB.

But I suspect it's not in my case.

The query in question runs fine when I spoon-feed it manually. It's going
south when I load it in code. I've written all the parms to Debug.Print and
then pasted them into a manual invocation of the query one-by-one and it worked
also.

I'm dead in the water on this one.

Anybody been here?
--
PeteCresswell

Per (Pete Cresswell):
Fixed it. Didn't find it....but I fixed it....

Deleted the Append query in question after copying the SQL.
Created a new query, pasted the SQL into it....Ran a-ok.

Sheesh!!!!
--
PeteCresswell

"(Pete Cresswell)" <x@y.z> wrote in
news:qq1ht0lpbt4opc1jp6td8t7etj0bdftccf (AT) 4ax (DOT) com:

Sounds like a case where the compilation of the query was out of
synch with the SQL text of the query. I've seen that and the
solution you found has always been the only way to fix it.

However, do note that it's possible with queries that exhibit that
problem to have it recur in the new query, as well. There appear to
be certain types of SQL that are susceptible to this kind of
problem. I've never been able to identify exactly what those
characteristics might be, however, but I have noted that it seems to
emerge by editing the SQL (whether directly or through the QBE) and
running it without saving first.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

Pete, did you have Name AutoCorrect turned off (Tools | Options | General)?

I've also experienced Access get the field names thoroughly confused when
this is turned on.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps.org.

"David W. Fenton" <dXXXfenton (AT) bway (DOT) net.invalid> wrote

"Allen Browne" <AllenBrowne (AT) SeeSig (DOT) Invalid> wrote in
news:41d8d4e0$0$8121$5a62ac22 (AT) per-qv1-newsreader-01 (DOT) iinet.net.au:

FWIW, that would *never* have caused me issues, because:

1. if I'm working in A2K, I've turned it off A LONG TIME AGO!

2. I've encountered the problem most often in A97, where there was
no such "feature."

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

Per Allen Browne:
No, but it's turned off now. Sounds like an excellant idea...I hope I remember
to keep on doing it...
--
PeteCresswell