What is this entry?

[Lou_Reed]

In the attached file is a db with Query3. I am curious since I used Query2 and a table to make Query3, why did I get Exprs001 in one of the entries in Query3, as it relates to Query2?

I do not see it in Query2. So it must have been created when I created Query3.

How did it get there?



Respectfully,

Lou Reed

[pbaldy]

You have the first name field twice; it aliases the second instance of it.

[Lou_Reed]

Okay, thanks I will make the correction.

Respectfully,

Lou Reed

[Lou_Reed]

When I opened up the db file and then Query3, first name entry was there twice with no alias. I then downloaded the file that I attached in post #1 and unzipped it and opened the db up, and went to query3. Again the first name entry was there twice with no alias. So what happened to the alias? We know that it is there. I knew it was in query3 when I zipped and uploaded the db. What happened to it? Did it change back into first name field somewhere along the way.

Please understand that I am quite serious and although the tone of the post may sound like I am joking. I am not where did the alias go?

Seriously.

Any help appreciated. Thanks in advance.

Respectfully,


Lou Reed

[pbaldy]

I'm not at my computer, but wasn't it in query2?

[Lou_Reed]

In the attached file is a db with Query3. I am curious since I used Query2 and a table to make Query3, why did I get Exprs001 in one of the entries in Query3, as it relates to Query2?

 I do not see it in Query2. So it must have been created when I created Query3.

 How did it get there?

Here is the original explanation. Query2 was used to create Quer3. Thus one could say if one wanted to that it was in both queries. No matter,
Exprs001 is in neither query now. That is my question. It changed from Exprs001 back to FirstName. That is okay. The modified query now has
only one FirstName entry. That is my question, again. What happened to Exprs001, did it change back to FirstName? It must have. If it did then the purpose of the question is moot.

I saw something that I could not identify in my design view of the query and now it is gone. Whathe double hockey sticks going on?

This was clearly unexpected.

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[pbaldy]

The cause of the problem was in query2; the alias can be seen in the field list of query2 when viewing query3 in design view. You can start a query and add a field twice and it won't be aliased until you run the query and Access realizes you've got the same field twice. Once you delete the second instance, you will no longer see the alias.

[Lou_Reed]

Okay, thanks for your input. It was very helpful. It is just one those annoying you see in MS Access 2010 that just makes you wonder where did that come from?

I understand your explanation. I think the best idea is to not make double entries. Again, thanks for your input.

Respectfully,

Lou Reed

[pbaldy]

No problem Lou.