Well, you'll have to make that decision, but if you're going to SQL Server my question would be why go through VFP in the first place???

So I would say 3 and possibly 1 are the solutions to work with although that may still need a com object if you use VFP in the middle.

+++ Rick ---


>Dr. Strahl, thanks for maintaining those pages. I hadn't looked at them in a while and I just noticed that you updated them on January 2.
>
>
>I'm going to look at the parameter array issue once I get my hands on the production release of VFP8. I am currently trying to decide whether it's better to
>
>1. Create a data-access class .cs that accepts parameters, does regex's on them to block injection attacks, create a VFP Stored Procedure string, and pass that string to a VFP stored procedure.
>
>2. Create a VFP COM object to take parameters as XML, have .cs clients pass XML documents with parms to the VFP COM object, let VFP do all the work and convert the response to XML for the caller.
>
>3. Create a data-access .cs that accepts parameters, does the regex stuff to purify them, but runs SQL strings raw against a DBC with ADO.NET and manipulate datasets within the class, which ultimately returns a typed result to the caller.
>
>
>Any comments on these options (in a current project I am experimenting with all 3) would be greatly appreciated.