There has to be an error in the way Access is interpreting your dynamic SQL
statement.
Is there any chance that the user has spaces in his field names, and you
have not included square brackets around them? Any chance the code is
looping too many times? Trying to use criteria on a calculated field instead
of repeating the entire calculation in the WHERE clause?
It would be really instructive if you could Debug.Print the resultant SQL
statement when it fails: are you able to visit the client and do that, or
else send him a little test case that will log the failing query statement?
A97 was thoroughly tested in Win98, so I would be very surprised if that
combination were an issue. Is it possible he has other bad combinations? For
example, is he trying to use DAO 3.6 with A97 instead of DAO 3.51?
This answer feels pretty incomplete, but hopefully it is of some use. 60
fields is certainly not the problem, so the issue must be elsewhere.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Steve" <sp**@nospam.spam> wrote in message
news:RB*****************@newsread2.news.atl.earthl ink.net...
An Access97 database I wrote contains a dynamic query whose results get
exported to Excel. I have WindowsXP and Access97, 2000 and XP installed. When I run
the query, it runs trouble free. A customer with Windows98 and Access97 on
three different machines runs the query on any of the three and gets error 3190
Too Many Fields Defined. To run the dynamic query, fields for the query are
picked from multi-select listboxes. If one selected every field in all the
listboxes, there might be sixty fields. The customer gets this error no matter how
many fields he selects. Help says error 3190 occurs if the query contains more
than 255 fields. Does anyone have any ideas what might be causing the error
message to appear?
