>Hi William,
>
>Nope, that doesn't work either. I tried calling one of the other stored procs that the guy wrote an it works fine from VFP. I even went as far as writing sample calling programs in VB 6 (*gasp*) and C#.
>
>Strange thing is that the C# program using OleDbCommand.ExecuteReader() to a OleDbDataReader works. However, since the VB 6 call fails too, I'm wonding if it might have something to do with the stored proc and ADO... either way I got to push it back to the guy who wrote the stored proc.
>


Well, we discovered what it was. Maybe others know this, but for those who don't and are interested, the problem was resolved simply by adding a SET NOCOUNT ON in the SQL Server stored proc. I don't know enough about the technical aspects of SQL SPs and their interaction with ADO to know why this matters, but it does and apparently the .NET OleDbDataReader can handle it and ADO 2.8 can't.



- Brian