>That Sir, is exactly what Im doing. I had searched the UT on the keyword "parameter" (thinking that it was a parameter issue) and seen that there are issues with the oledb provider but didnt realize that it is off limits for now. I assume that a patch is in the works a MCS.
>
>Note that when I removed the "parameter" goodies it did create the XML schema and everything seemed to work.
>
>There must be workarounds for this. Ill try searching the UT on some other keywords.
>
>Best regards,
>
>Todd

You can do a lot but not with the some of the built in designers that require the table's layout. I've seen mention of making the provider more compatible with .NET but do not have any detail. Maybe someone in the know will chime in. You should check Rick Strahl's whitepaper on .NET Interop for Visual FoxPro at http://www.west-wind.com/presentations/VfpDotNetInterop/vfpDotNetInterop.htm. It has a section on OLEDB that mentions this problem.

Good Luck,