ASP and ADO Gotcha - Duplicate Field Names in a Query

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss Content Posted by Leon Platt » ASP and ADO Gotcha - Duplicate Field Names in...

ASP and ADO Gotcha - Duplicate Field Names in a Query

Rate Topic

Display Mode

Topic Options

Author

Message

Leon Platt

Posted Monday, July 16, 2001 12:00 AM

SSC Journeyman

Group: General Forum Members
Last Login: Saturday, February 10, 2007 12:11 PM
Points: 91, Visits: 1

Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/lplatt/aspandadogotchaduplicatefieldnamesinaquery.asp

Post #581

mmaslanik

Posted Wednesday, August 08, 2001 5:59 AM

Forum Newbie

Group: General Forum Members
Last Login: Tuesday, October 05, 2004 5:41 AM
Points: 1, Visits: 1

That's wonderful, but what is the solution?

Post #20056

GRN

Posted Wednesday, August 08, 2001 6:11 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, June 08, 2006 2:26 AM
Points: 170, Visits: 1

use a alias i suppose !!

Post #20057

robiwon

Posted Thursday, August 09, 2001 3:42 PM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, June 29, 2005 6:07 PM
Points: 1, Visits: 1

Is this article for real? You must be very new to ADO programming to just be hitting this.

Post #20058

Leon Platt

Posted Saturday, August 11, 2001 9:35 PM

SSC Journeyman

Group: General Forum Members
Last Login: Saturday, February 10, 2007 12:11 PM
Points: 91, Visits: 1

quote:
Is this article for real? You must be very new to ADO programming to just be hitting this.

That would be an incorrect assumption but thanks for the feedback anyway. The thing is, I probably never would have run across this if it wasn't for the cut and paste programming I happend to be doing at the time. Typically I would have written the sql statement by hand in which case I would have aliased the fields accordingly. Yes GRN - you are correct

quote:
use a alias i suppose !!

Although there are several solutions to this problem the best is to alias the rating as "Article Rating" and "Book Rating", thus no ambiguity. The purpose of this Tip was not to uncover some deep dark secret of ADO but rather to give other programmers something to think about when creating sql statements that return record sets in ADO.

Post #20059

Andy Warren

Posted Tuesday, August 14, 2001 5:06 AM

SSCertifiable

Group: Moderators
Last Login: Thursday, May 09, 2013 12:38 PM
Points: 6,462, Visits: 1,384

I agree with Leon that this isn't so much about ADO as it is best practices. If you're aliasing your tables and cols correctly, you'll never see this. Just out of curiousity, can anyone tell me if this is a bug or a feature of ADO?

Andy

Andy
SQLShare - Learn One New Thing Each Day
SQLAndy - My Professional Blog
Connect with me on LinkedIn
Follow me on Twitter

Post #20060

BobAtDBS

Posted Tuesday, February 05, 2002 11:34 AM

SSC Veteran

Group: General Forum Members
Last Login: Monday, October 10, 2011 2:00 PM
Points: 297, Visits: 329

Once the Join is done, there are no P. and A. qualifiers anymore. You simply have to alias the fieldnames to something meaningful. I suppose it's considered a 'feature' since many times the identically named fields would have identical data (but then why return both?).

Student of SQL and Golf, Master of Neither

Post #20061

« Prev Topic | Next Topic »

Permissions