-
We have Sybase 11 here and I've noticed that the Environment Designer for VB6/E does not import stored procedurs properly. If the proc only returns records it's great. If it takes parms and returns only parms that's ok too. BUT, if it takes parms and returns records we're out of luck. Basing a CMD object on such a SP yes a CMD object w/no fields. Basing it on a 'exec SP_name' code however works great. Both MS and Sybase have punted at this. Has anyone seen this and found a work around? I'm having to hard-code my SQL code and I hate it! It worked fine at my prev job with MSSQL.
-
what if you try to use a recordset and connection (no designers) to pass parameters and retrieve results.
Like this:
dim cn as connection
dim rs as recordset
set cn = new connection
cn.open <connectionstringhere>
set rs = cn.execute("sp_namehere param1, param2")
msgbox rs.fields(0).value 'check for return values
does this work ok?
Tom
