Bruce Tong wrote:
>
>
> Another window appeared and said "Error while executing the query. ERROR:
> The field being ordered by must appear in the target list (#1)."
>
> Since I hadn't specified any sorting, the "order by" part of the message
> had me confused. I decided to have MS Access show me the SQL it had
> generated:
>
I finally figured out what the heck is going on with this order by
problem in MS Access. I tested your query on a computer that has older
versions of the Microsoft Jet db engine on it and guess what? It does
the same thing you described! The reason that I used to have the
problem and it miraculously went away was because I installed Visual
Basic 5.0 and it upgraded the MS Jet dll's.
Your right about the snapshot. It still tries to throw the order by
clause in there.
But, here's a simple workaround that you can easily try. When looking
at your query in Access, right click on the fields area and select
"Totals". This will add a group by clause but it won't have any real
effect, other than it will let your query run!
So, there are two things you must do to fully fix the order by problem:
1. Upgrade the MS Jet DLL (this is the real problem here)
2. Get the patch for the order by/group by from our web site (it will be
in postgres 6.4 also)
Interestingly, even if you get the postgres patch like we have here, the
older MS Jet engine will still not let you sort the columns the way you
want, because it always throws that same old order by in there.
The working version of \windows\system\MSJET35.DLL is 3.51.0623.4
The broken version I tested was 3.50.3602.4
I'm not sure at what release they fixed this problem.
I will dig around on MS web site.
Does anyone know if its OK to redistribute the MS JET DB Engine DLL,
like with our ODBC driver for example??? (That thing is big too,
1MB!!!)
For that matter, is there a simple way to get it from Microsoft?
Byron
