>The problems aren't necessarily with remote views with more than 1 table for updating. Its trying to create the view with the view designer when more than 2 tables are involved.
>
>PF
>
>>What Problems did you have with setting up a remote view with more than one table for updating? The reason I ask is that I haven't had any problems utilizing more than one table in a view that was updateable. I beleive the largest view definition I am using is 4 tables with creating/setting indexes prior to dbsetprop on setting the buffermode.
>>
>>Pat.
Well, that can be pretty hairy. Been there done that. But once you get over that hurdle, things smooth out pretty good.
Pat.
Patrick L. Stovall
Senior Architect/Developer
MCP - C#
VeroQuest
P.O.Box 7216
Kalispell, MT 59904