Getting an error 3825, complaining about multi-valued fields, but none are involved. (2 Viewers)

[GPGeorge]

You've talked about tables and columns but not described nor shown any of them in your responses.

In that environment, it's difficult for anyone to know what might have happened, nor to guess at possible reasons for the problem.

 

[Papa_Bear1]

You've talked about tables and columns but not described nor shown any of them in your responses.

In that environment, it's difficult for anyone to know what might have happened, nor to guess at possible reasons for the problem.

True ----
In this case, I've described the problem. From what I can see here, the names of tables and fields is irrelevant - right? The problem is that the same query that works on *some* tables, suddenly doesn't work on others, and exhibits an error that is completely erroneous - talking about multi-valued fields as the root of the problem and yet there are NO multi-valued fields involved at all.

Proof of this is that, as I've noted, I've reworked it, naming the fields, rather than using "*", and for some reason - that works. It is the same set of fields, so, it seems at best the error is simply misleading - at least as far as the actual cause! I suppose that isn't all that rare in our VBA world - sometimes the error is down pretty low - and the message just doesn't float up to the top!

 

[GPGeorge]

The inquiry at hand isn't about the names of tables or fields. The inquiry is about datatypes, e.g. like the one in your error message regarding a multi-value field.

So, while you resolved your problem by switching from the wildcard to specifying field names, it's still ambiguous about why there was a problem.

I guess the point is this. The more detail one shares about a problem, the more likely it is that others will be able to recognize potential failure points. What is hard or objectionable about sharing details has always eluded me.

 

[Papa_Bear1]

The inquiry at hand isn't about the names of tables or fields. The inquiry is about datatypes, e.g. like the one in your error message regarding a multi-value field.

So, while you resolved your problem by switching from the wildcard to specifying field names, it's still ambiguous about why there was a problem.

I guess the point is this. The more detail one shares about a problem, the more likely it is that others will be able to recognize potential failure points. What is hard or objectionable about sharing details has always eluded me.

Right - totally get it - in general. I just so happen to not be able to upload sample code easily. I'd have to spend more time than I have creating something I can/should/be allowed to upload - and then - it probably wouldn't end up looking close enough to the original to be worth inspecting. So, I try to supply what I expect is enough to understand the problem. If I could easily just upload code and data and examples - I certainly would. I just can't.

I really appreciate the time, effort, comments, ideas, and advice, that I get here. Having this Access-focused resource is fantastic. So, I apologize if my question is under par... I'm doing the best I can in the time allotted...

 

[cheekybuddha]

So, I try to supply what I expect is enough to understand the problem.

Since you don't understand the problem, how do you know what is enough to understand it?