Sort Oder not as I planned

[AkAlan via AccessMonster.com]

I have a view created with a sort order on the SiteName field but it sorts in
the SiteID field. Am I missing simething here?

SELECT DISTINCT TOP 100 PERCENT dbo.QcCar.SiteID, dbo.QcSites.SiteName
FROM dbo.QcSites RIGHT OUTER JOIN
dbo.QcCar ON dbo.QcSites.QcSitesId = dbo.QcCar.SiteID
WHERE (dbo.QcCar.QcFinalReviewDate IS NULL)
ORDER BY dbo.QcSites.SiteName

 

[Sylvain Lafontaine]

There are no sorting order in Views because they are interpreted like
tables. Under some circonstances, adding a TOP 100 PERCENT will give you
the impression that this work but as you might now see, this doesn't work
100% of the time on all platforms/applications.

Use a Select statement to query your view and add your Order By to it.

 

[AkAlan via AccessMonster.com]

Perfect, Thanks

There are no sorting order in Views because they are interpreted like
tables. Under some circonstances, adding a TOP 100 PERCENT will give you
the impression that this work but as you might now see, this doesn't work
100% of the time on all platforms/applications.

Use a Select statement to query your view and add your Order By to it.

I have a view created with a sort order on the SiteName field but it sorts
in

[quoted text clipped - 6 lines]

WHERE (dbo.QcCar.QcFinalReviewDate IS NULL)
ORDER BY dbo.QcSites.SiteName

 

[asus]

I have a view created with a sort order on the SiteName field but it sorts
in
the SiteID field. Am I missing simething here?

SELECT DISTINCT TOP 100 PERCENT dbo.QcCar.SiteID, dbo.QcSites.SiteName
FROM dbo.QcSites RIGHT OUTER JOIN
dbo.QcCar ON dbo.QcSites.QcSitesId =
dbo.QcCar.SiteID
WHERE (dbo.QcCar.QcFinalReviewDate IS NULL)
ORDER BY dbo.QcSites.SiteName

 

[Bob Snedden]

Dear Sylvain,

I have an important customer who has upgraded to SQL Server 2005 with 9 ADP
databases I have designed for them.

This upgrade was done for replication purposes for other SQL Server
applications not my databases.

From you reply to this post - Am I now having to update all comboboxes to
use store procedures or to use SELECT statements from Views in order to get
sorted lists?

This looks like a mountain of work but I assume because 2005 treats Views as
Tables unlike 200.
--
Bob Snedden, MCT, MCSD.Net

There are no sorting order in Views because they are interpreted like
tables. Under some circonstances, adding a TOP 100 PERCENT will give you
the impression that this work but as you might now see, this doesn't work
100% of the time on all platforms/applications.

Use a Select statement to query your view and add your Order By to it.

 

[Sylvain Lafontaine]

You can try replacing the TOP 100% in the Views with something like TOP
2000000000.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)

Dear Sylvain,

I have an important customer who has upgraded to SQL Server 2005 with 9
ADP
databases I have designed for them.

This upgrade was done for replication purposes for other SQL Server
applications not my databases.

From you reply to this post - Am I now having to update all comboboxes to
use store procedures or to use SELECT statements from Views in order to
get
sorted lists?

This looks like a mountain of work but I assume because 2005 treats Views
as
Tables unlike 200.