>Naomi,
>
>Sorry that it has taken me so long to get back to you and Cetin and the rest of the UT community (is anyone else listening?) on this issue. I have been working with MS Product Support Services to identify the cause of the problem, and identify a work around.
>
>The basic cause of the problem: there is a bug in the OLE DB Provider for Visual FoxPro. It apparently allocates memory for inputting the stored procedures in the VFP database. However, the size of that buffer is not large enough for the total of stored procedures in my database. I believe their buffer is 100KB, and my stored procedures take up 180KB.
>
>I don't know why no one else has run across this bug. Maybe the VS2005 ATL OLE DB Consumer Wizard is the only program that actually asks the OLE DB Provider for Visual FoxPro for information about stored procedures.
>
>In any case, for my purposes, I don't think I need information about the stored procedures for the ATL OLE DB Consumer Wizard to create the classes I need. So, I can make a copy of my DBC, strip out the stored procedures, and use that as the source for ATL OLE DB Consumer Wizard. At least, I will give that a try and see how it works out.
>
>Thanks again for your help.
>Jim

Jim,

This is very important information and there good investigation of the problem from your side.

Now, just out of curiosity - why your SP is so large? I bet you're using VFP native RI builder...