[AccessD] Alias Table Name

Thanks to all for their replies.  

Rocky
 




 	
	

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman
Sent: Monday, April 14, 2008 8:37 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Alias Table Name

Rocky,

  For some, it's just a matter of formatting and/or saving some time as Mark
and Susan said.

  But also in the past, Access had a hard "compile" limit on queries of 64K.
A lot of developers used that technique to shorten table references to get
around that problem enabling them to run more complex queries.

Jim. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at
Beach Access Software
Sent: Monday, April 14, 2008 11:02 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Alias Table Name

Dear List:
 
In a legacy app I came across some queries which in the QBE had 'alias'ed
tables (or maybe queries).  one called P was joined to one called A.  The
list of field names didn't correspond to any table.  There are a lot of
queries so I didn't look through them to see if a query matched the field
list in either P or A.
 
But I've never seen this done.  Why would you do this?  How can you tell
what the source of the fields in the aliased table is?  Is there some
performance gain or other reason for doing this?

MTIA,
 
Rocky
 


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

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

No virus found in this incoming message.
Checked by AVG. 
Version: 7.5.519 / Virus Database: 269.22.13/1376 - Release Date: 4/13/2008
1:45 PM