Re: Why Doesn't An Index Download In The Correct Order?

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Are you telling CA to use this exact statement? Or just something like 
select * from view? I would expect the ORDER BY in the view to be 
honored, as I think you do, too, but not sure.

On 4/5/2013 12:02 AM, w 4038 wrote:
> All,
> I have two tables with the same data layout. TableA is inventory from last month. TableB is the current inventory.
> The goal is to put both tables side by side in a spreadsheet to compare last month to the current month.
> Most of the rows are duplicates and exist in both tables. Some rows are new items in the current month. Some rows existed last month but no longer exist in the current month.
> The following SQL statement creates a view and the side by side comparison is perfect. (Thanks to B Hauser for the coalesce suggestion)
> create view qgpl/viewAB as
>   Select * from
>   (select * from qgpl/tableA
>            full outer join qgpl/tableB
>            on f1file = f2file
>            order by coalesce(f1lib,f2lib),
>            coalesce(f1file,f2file), coalesce(f1mbrname, f2mbrname) ) as t
> But when I download the view using Client Access, the order is not maintained. Does anyone know why?
>
> Thank you