Function of colon between table names when query in design view

  • Follow


I am looking at a field from a query that is in design view.  Inside the 
field are two field names from the same table which are separated by a colon. 
 For example, Old and New are both fields from tblReplace and appear like 
this Old:New in design view.  I believe the colon concatenates the field Old 
and New into a new field when you change the query view to datasheet view.  
Am I correct?

Also, in a completely separate question if you are looking at a query in 
design view and there is a field in the (Field:) row, a table in the (Table:) 
row, and Group By in the (Total:) row what function will the Group By option 
perform when you change the query view to datasheet view? 

0
Reply Utf 6/7/2010 6:11:51 PM

If you are talking about having a field "block" with something in it like
   Field: Old: New
that should be assigning an alias "OLD" for the field named NEW and should not 
do any concatenating at all.

It will consolidate all the same values into one row.  For instance if you had 
a table with first names and last names show only the first name and GROUP By 
the first names you will see one row for everyone who has the first name JOHN.

If you add the first name field again and set the Total to COUNT you would see 
something like

FIrstName   CountOfFirstName
JAMES_________8
JEAN__________1
JOHN__________22

If you have multiple fields and group by them, then the group by is done on 
the combination of the fields.


Jazz wrote:
> I am looking at a field from a query that is in design view.  Inside the 
> field are two field names from the same table which are separated by a colon. 
>  For example, Old and New are both fields from tblReplace and appear like 
> this Old:New in design view.  I believe the colon concatenates the field Old 
> and New into a new field when you change the query view to datasheet view.  
> Am I correct?
> 
> Also, in a completely separate question if you are looking at a query in 
> design view and there is a field in the (Field:) row, a table in the (Table:) 
> row, and Group By in the (Total:) row what function will the Group By option 
> perform when you change the query view to datasheet view? 
> 
0
Reply John 6/7/2010 7:05:17 PM


Thank you for teaching me about the proper vocabulary i.e. "block" and 
helping me understand how the colon : and Group by work.  

I do have one more question now about the colon.  What function could 
assigning an alias accomplish in a query?

"John Spencer" wrote:

> If you are talking about having a field "block" with something in it like
>    Field: Old: New
> that should be assigning an alias "OLD" for the field named NEW and should not 
> do any concatenating at all.
> 
> It will consolidate all the same values into one row.  For instance if you had 
> a table with first names and last names show only the first name and GROUP By 
> the first names you will see one row for everyone who has the first name JOHN.
> 
> If you add the first name field again and set the Total to COUNT you would see 
> something like
> 
> FIrstName   CountOfFirstName
> JAMES_________8
> JEAN__________1
> JOHN__________22
> 
> If you have multiple fields and group by them, then the group by is done on 
> the combination of the fields.
> 
> 
> Jazz wrote:
> > I am looking at a field from a query that is in design view.  Inside the 
> > field are two field names from the same table which are separated by a colon. 
> >  For example, Old and New are both fields from tblReplace and appear like 
> > this Old:New in design view.  I believe the colon concatenates the field Old 
> > and New into a new field when you change the query view to datasheet view.  
> > Am I correct?
> > 
> > Also, in a completely separate question if you are looking at a query in 
> > design view and there is a field in the (Field:) row, a table in the (Table:) 
> > row, and Group By in the (Total:) row what function will the Group By option 
> > perform when you change the query view to datasheet view? 
> > 
> .
> 
0
Reply Utf 6/7/2010 9:07:36 PM

2 Replies
478 Views

(page loaded in 0.061 seconds)

Similiar Articles:













8/1/2012 10:28:27 AM


Reply: