Gates Is Antichrist
Well-known Member
- Joined
- Aug 15, 2002
- Messages
- 1,961
This is somewhat an academic question. Consider a query with one source table only. In the query designer, you can select Table from a dropdown (which in this case has only 1 entry). Yet you can also just hit the delete key on the field, and it'll work the same.
The difference is that the underlying SQL is affected. If a table is selected in the query design interface, the SQL is qualified - e.g. Table1.Field1. If table is not shown in the design (e.g. you "hit delete key") then the SQL has just Field1.
My question is whether there is an esoteric benefit to the qualification. I'm tempted to start deleting them, to reduce visual noisiness - both in the designer and the SQL.
And how about you speed wizards - does the qualification or lack impact performance? I guess that is really a Jet question rather than Access...
Finally, in fact, the table qualification is optional even with multiple FROM tables! Again, I wonder if there is a meaningful speed consideration; is there just a one-time resolution or does non-qualification cost you?
The difference is that the underlying SQL is affected. If a table is selected in the query design interface, the SQL is qualified - e.g. Table1.Field1. If table is not shown in the design (e.g. you "hit delete key") then the SQL has just Field1.
My question is whether there is an esoteric benefit to the qualification. I'm tempted to start deleting them, to reduce visual noisiness - both in the designer and the SQL.
And how about you speed wizards - does the qualification or lack impact performance? I guess that is really a Jet question rather than Access...
Finally, in fact, the table qualification is optional even with multiple FROM tables! Again, I wonder if there is a meaningful speed consideration; is there just a one-time resolution or does non-qualification cost you?
