[AccessD] Undocumented Access SQL syntax - Derived tables

Ok, but, I'm just not visualizing what it actually DOES.  (Union, I know
what that does, so I can think of places to put it ... i.e., adding
<ALL> to a combo ...)
So, I guess I am looking for an example like "In an Invoicing screen I
used this to do blah-blah" or "in a calculated column of a widgets
query, I used it to yada-yada"

Steve


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Friday, July 30, 2004 8:29 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Undocumented Access SQL syntax - Derived tables


Hi Steve

It is not a universal trick. It is just a tool like, say, a union query
- sometimes it's useful, in some apps you may not use it at all.

Just have it in mind and it will pop forward when you need it!

/gustav


> Quite interesting, but, I'll admit, I don't see the application of 
> this ... Could someone elaborate how I could make my applications 
> better using this bit of sql in an app?

-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com