Hi, all...

We are moving our VFP app into a .NET environment, yet I'm still looking to use VFP in the middle tier to supplement areas where .NET still doesn't cover everything.

One example - being able to perform set-based operations against an ADO.NET datatable - Kamel's article in the most recent UT Magazine has a great example of passing a dataset to a VFP7 COM object that can convert the dataset to a cursor (XMLTOCURSOR), and then being able to pass a SQL string to the VFP COM object to query against the cursor, and then bring the result back into the dataset. I do a good amount of 'after the fact' querying to re-group sets of data, so his utility is a god-send.

One problem...I may run into some resistance from colleagues, etc. who are less than thrilled with introducing VFP7 into a .NET environment. Most anticipated reaction will be "it's not managed code", "COM is outdated and isn't stable', blah blah blah.

Can anyone give me some good strong ammunition if I run into this?

Thanks,
Kevin