I am guessing you were talking to me since Dizzy posted a comment on my article. I'm Steven, not Brian. Thanks though.
I just posted my method for ensuring a sort value exists on the first insert in my article as an update. I suppose I should have provided more detail on how to do that part the first time.
Sorry, I did not read your original question correctly.
I look forward to your post on this code. It could be quite helpful.
To answer your question, I use it on relational tables all the time by hacking WA so the list page (WA calls Results) is a filtered recordset. You have to go through and ensure you pass the filtering ID through the Insert, Update, and Detail pages. For example, if I understand what you are doing, I have a number of image galleries. I use a WA DA wizard set of pages to manage the galleries. I include the sort order modification to that page.
Next, I add a button to the button row from WA (Details, Edit, Delete becomes Images, Details, Edit, Delete). Then I make a set of WA DA wizard set of pages for the images. Add the WHERE portion to the recordset, and pass the MasterKey in the form url's and links. It is about 10 edits I think, but still a bit of a pain. Then I apply the sort method to those pages.
On menus and submenus, I do the same thing one one table where parentid = 0 means it is a main menu item.
I look forward to seeing how that compares with what you are doing here.
There have been a number of posts over time asking for WA to look at RECORDSET management as an option instead of just TABLE management. I hope that we see that in an upcoming version.
P.S. I should have said you have to be sure and pass the filter ID to all the WA DA pages. The ones I mentioned are the main pages, but, for example, if you don't ensure it passes through the delete page, you won't get returned to the correct results page.