Hi, guys,
What's up with (p.35) using IDataParameter() instead of a SQLParameterCollection? For one thing doesn't the latter implement the former? In any case I can't get the former to convert to the latter. In the BuildIntCommand() function, for instance, I use "ByVal parameters As IDataParamter()" and this won't convert in the body of the function on the line, "Dim command as SQLCommand = BuildquesryCommand(SPName, parameters)" . Yup, it doesn't like parameters being type IDataParameter.

I suppose I can substitute SQLParameterCollection, right? But why is the book using IDataParameter?

Thanks .... Paul

OK, I'll reply to my own post. I'll bite. Maybe somebody can lend a word or two on this subject after hearing about my solution.

Again, this is in Core.DLL, the DBOject class: I've replaced references to IDataParameter() with SQLParameter() and it works fine. I did not use SQLParameterCollection - that had problems. I think the problem was that I couldn't get it to convert for use in the command object. Yeh, that's what it was.

So, I am rather new to the intermediate level and don't really get why the book suggests passing IDataParameter() or why nobody else reported having problems with it. Anybody with a bit 'o help to understand that?