B
Bruce Rudd
Guest
Sounds like the application might be assuming the procedure has two parameters without checking to see if that is correct first. It would probably be a good idea for the application to call SQLProcedureColumns prior to the SQLBindParameter calls for the execution of the procedure. Then the app would know how many parameters the procedure has, if they are input or output and what the data types are. This will ensure the application binds the parameters correctly for that stored procedure.
Continue reading...
Continue reading...