Matt,
I have a couple of forms that seem like they will be particularly challenging, since they use a VCR control to do do "SKIP 1" or "SKIP -1" on the master table and that automatically moves all the pointers in the related tables.I'm afraid that's not really a proposition with SQL Server data unless you are dealing with data subsets that can be pulled to the client- once the data is in a cursor you can index and use "set relation" in the normal way.
However, since you need to find a non-VFP way to achieve the goal, your best bet is to spend some time documenting exactly what is going on so you can carve an efficient SPT or SP to pull the data. You may well end up with joined tables or calculations performed in SQL rather than on the fly with related tables. Also you might want to consider a day or two of expert SQL Server consulting, but you'd want a real "expert" rather than a general practitioner who may not understand data as well as you do.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1