I am taking a wild swing at this one. I do hope this fixes the bug, but it's hard to tell when the bug is so spotty. I think this is more of a bug with the DB than PRADO, but hey, this should fix that quirk.
I didn't think this was necessary because.... wouldn't the DB return the table in the order of insertion?
apparently, randomly, it switches rows unless explicitly ordered
I am taking a wild swing at this one. I do hope this fixes the bug, but it's hard to tell when the bug is so spotty. I think this is more of a bug with the DB than PRADO, but hey, this should fix that quirk.
I didn't think this was necessary because.... wouldn't the DB return the table in the order of insertion?
apparently, randomly, it switches rows unless explicitly ordered