>>This doesn't sound like a multi-table remote view. If it was, then adding a record would always add to both tables, not conditionally on any field. I see and understand that you're doing the with SP, but I STILL DON'T see how this could be accomplished conditionally using a multi-table remote view.
>>
>>Sorry if I'm just being dense here, I haven't done a whole lot with backend data, yet, and I'm just "fact & technique gathering".
>
>Well part of the problem is that you have no control with a RV - which is why I don't use them. With RV - I BELIEVE - that if you insert into the view and both tables are set to be updated - that you will just create a null-filed record in the second table.
>
>That is why I use SP with data-objects that get my SPT cursors. I avoid the wrapper effect of a RV and can get "in between" the two updates with hooks to make decisions about whether to ever create the record in the second table or not.

OK, I get it now. You can't do what you're doing with a single RV to two tables, but you can do it with 2 RV's or via your method with SP's. But you certainly made it sound like a single RV could do this, I was just wondering "How?".

Thanks.