Re: [GENERAL] Re: [INTERFACES] ODBC Driver -- Access Order By problem solved!!!
> > Since I'm learning SQL in my spare time, I tend to use these feature in MS > Access and PgAccess to point me in the right direction or sometimes > confirm, or deny my assertions. > > I like psql, but its not the kind of tool which suggests other > alternatives. It just says "this part is bogus." That's fine, but when I > fail to get it right after a dozen attempts, its nice to let something > else take a stab at it. Please tell use what else psql can tell the user. We have \h and \d commands. -- Bruce Momjian | 830 Blythe Avenue [EMAIL PROTECTED] | Drexel Hill, Pennsylvania 19026 + If your life is a hard drive, | (610) 353-9879(w) + Christ can be your backup.| (610) 853-3000(h)
Re: [GENERAL] Re: [INTERFACES] ODBC Driver -- Access Order By problem solved!!!
> FWIW: > > I seldom do much more than add the tables in MS Access's stupid > query design thingy. I immediately use the menu to view SQL and > just type the SQL I want. Obviously, different folks think different ways, > and maybe you actually understand and like that MS Access point and click > interface that I hate, but I want to be sure you're at least aware that if > it sticks an ORDER BY in there that you never asked for, you can just rip > the damn thing out in the SQL view and then run the query... At least, > that's how I make it give me the SQL I really want, instead of the SQL it > thinks I want, which it never gets right anyway. Since I'm learning SQL in my spare time, I tend to use these feature in MS Access and PgAccess to point me in the right direction or sometimes confirm, or deny my assertions. I like psql, but its not the kind of tool which suggests other alternatives. It just says "this part is bogus." That's fine, but when I fail to get it right after a dozen attempts, its nice to let something else take a stab at it. Bruce Tong | Got me an office; I'm there late at night. Systems Programmer | Just send me e-mail, maybe I'll write. Electronic Vision / FITNE | [EMAIL PROTECTED]| -- Joe Walsh for the 21st Century
Re: [GENERAL] Re: [INTERFACES] ODBC Driver -- Access Order By problem solved!!!
Richard Lynch wrote: > > > FWIW: > > I seldom do much more than add the tables in MS Access's stupid > query design thingy. I immediately use the menu to view SQL and > just type the SQL I want. Obviously, different folks think different ways, > and maybe you actually understand and like that MS Access point and click > interface that I hate, but I want to be sure you're at least aware that if > it sticks an ORDER BY in there that you never asked for, you can just rip > the damn thing out in the SQL view and then run the query... At least, > that's how I make it give me the SQL I really want, instead of the SQL it > thinks I want, which it never gets right anyway. > > Hope that helps. > Thanks, I would probably agree with you, but it makes no difference if I like it or not, its our customers who want the graphical interface and FINALLY, we have a fix for it! They are most likely not the types who are gonna drop down to the pound sign and type some SQL into the monitor! And BTW, if you look at the SQL, you wouldn't even see the ORDER BY thing because this clause is placed on the "keyset" query, which is the collection of keys it uses to dynamically access rows in the query result (i.e. the Dynaset). Actually, I understand your hate of the Microsoft thing, but I only recently realized the benefit and power of this Jet database engine thing that Access uses. For example, it can update the results of a query that has several tables joined, right while your looking at the row on the screen, automatically translating the SQL2 syntax (i.e., INNER JOIN ... ON ...) into standard SQL that Postgres can use. Byron
Re: [GENERAL] Re: [INTERFACES] ODBC Driver -- Access Order By problem solved!!!
At 10:36 AM 7/24/98, Byron Nikolaidis wrote: >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. FWIW: I seldom do much more than add the tables in MS Access's stupid query design thingy. I immediately use the menu to view SQL and just type the SQL I want. Obviously, different folks think different ways, and maybe you actually understand and like that MS Access point and click interface that I hate, but I want to be sure you're at least aware that if it sticks an ORDER BY in there that you never asked for, you can just rip the damn thing out in the SQL view and then run the query... At least, that's how I make it give me the SQL I really want, instead of the SQL it thinks I want, which it never gets right anyway. Hope that helps. -- -- -- "TANSTAAFL" Rich [EMAIL PROTECTED]
