Glenn,

DTS might be a good option for you, as was suggested, but this probably isn't all that hard to do in .NET. You're just unfamiliar with where to start. Plus, it sounds like you want to do it in .NET so you can learn it. However, given that you want to use MM, I cannot give you any ideas on how to handle this because I don't use MM and don't know what the best practices would be in MM. So, I guess I'm just responding to your rant. <g>

~~Bonnie




>Thanks Victor, I will investigate the event object and see if I get any clues as to how to do this in MM.Net.
>
>I do appreciate your help and support and recognise that you cannot hold my hands over the keyboard. I am sorry but as a neophyte I feel like Sgt Schultz of Hogan's heroes "I know nothink"
>
>

<Rant>

>I guess I am pretty frustrated because if this were a VFP related question there would be at least a dozen fleshed out examples. I suspect that .Net does not lend iteself well to this kind of processing.
>
>I will continue to study my "VB.Net and SQL Server 2000" book and others to see if I can find an example. I have at least 12 different books on VB.Net and SQL 2000 and nowhere is there an example of this kind of "Data Processing". All examples are GUI intrerface / Data Store type examples.
>
>If this were VFP I would:
>

>update SqlData set field1 = vfp.field2, field3 = vfp.Field3 ... where id = vfp.id
>insert into sqldate (field1,field2,...) values (vfp.field1,vfp.field2,...) where vfp.id not in (select id from sqldata)
>

>Pretty simple stuff, oddly I have posted this question 2 times and have not even gotten a sketcy example to start coding. Elsewhere on this website is an ongoing thread regarding Object based data handling in .NET as compared to VFP cursor based DML. At this point in my exploration of .Net I must say that there is no comparison period!
>
>Kevin M. did not give me any clues and the documentation with MM.Net sheds no light on this either. Maybe I need to forget MM.Net for this type of processing and stick to VFP or use DTS as previously suggested because they are a better fit, and far less code.
>

</Rant>

>Whew! sorry for the rant, but I had to get it off my chest.
>
>
>>Gotcha!
>>
>>There is a base object in MM.NET called Event Object - not related to Events in .NET
>>
>>You can sub-class from this object to create your own Event Object to coordinate transactions from several business objects.
>>
>>The architecture that's we've followed in the past is to put all your validation in the business objects, coordinate the transaction and cross-bizobj validation at the Event Obj Level and do all your inserts into multiple table using Stored Procs with implicit sql transactions.
>>
>>This has worked out to be the fastest mechanism while working MM.NET
>>
>>Hope this helps!