Bruce & Kevin (and anyone else who's curious about the same thing),
I was able to make it work, and it works quite nicely.
I took Bruce's suggestion and thoroughly inspected the code generated by the templates, as well as the related methods in netweb.clw. After understanding exactly what the NetTalk template code was doing, I was able to create a generic source code loop that would mimic the NetTalk code.
I modified (slightly) an object we already used to build dynamic windows in our Windows app to provide the information I would need (such as field names, types, values, restrictions, etc.) to provide output that would then be inserted into the loop when generating the form.
The action page (where the form posts to) then receives the posted values, loads them back into a new instance of the object (as well as the session queue), and displays them for the user to approve (after the object validates the data using its own methods, already in use by our Windows app). Later in the process I actually commit those values to our Database ... which are then viewable in our Windows app.
It turned out to be very simple, and a lot easier than I was expecting it to be. What I haven't done yet, but might consider, is allowing for "real-time" verification of the fields (i.e. duplicating the "Send new value to server" feature of regular form field.
Thanks, Bruce and Kevin for your suggestions! NetTalk just got even more exciting.
Regards,
Flint