in reply to Re: Re: Re: Considerations on ordering
in thread Sorting

I would start with the other reply in this thread and go from there. I agree with the other poster that the requirements don't seem complete -- it might be worth posting a sample of the data from the database and hand-hacking a result of what you'd want that turned into. Right now we can only see an example of it not working.
  • Comment on Re: Re: Re: Re: Considerations on ordering

Replies are listed 'Best First'.
Considerations on ordering
by johnirl (Monk) on Aug 14, 2002 at 08:37 UTC
    Table 1.

    memory Value - 64456 2 76574 4 36577 8 76577 16 74657 - 76576 2 56756 4 -- 8 75676 16 98797 - 23432 2 43566

    Table 2.

    memory Value - 64456 2 76574 4 36577 8 76577 16 -- 32 74576 - 76576 2 56756 4 76457 8 75676 16 75766 32 32446 - 23432 2 34534

    Result

    memory Value1 Value2 2 54623 87686 2 34534 54675 2 24564 56464 4 56745 65646 4 34547 45644 4 -- 34251 8 45654 56454 8 64566 56563 8 58468 56565 16 77457 - 16 56864 81678 16 98754 65354 32 -- 56763 32 -- 64566 32 -- 67387 -- [0] 56345 64243 -- [0] 43587 65456 -- [0] 65464 45654

    Desired Result

    memory value1 value2 0 56465 54655 2 66455 64564 4 48765 35345 8 23451 66456 16 23526 68773 32 - 46145 0 87443 26452 2 25486 24764 4 - 25676 8 27798 23467 16 25667 - 32 - 66767 0 55279 21467 2 78743 26874

    Number of Value columns may vary. Highest memory values may vary.

    j o h n i r l .

    Sum day soon I'Il lern how 2 spelI (nad tYpe)