on 2022 Jan 05 1:28 AM
Hello, all Some of our stored procedures contain numerous parameters and the client program is not supposed to pass all of them (some get default values). We see in SQL Anywhere debugger that the values of parameters received are not the ones in the Parameters array of the SACommand. Some parameters, which show empty (null) in the code is received as "1" for some reason. Our question: is there a way to see the actual SQL command being created by the .NET code, so we could see why the values are messed up?
Thank you Arcady
Request clarification before answering.
As I said, I worked around this problem by not using the StoredProcedure type command at all. So, now I got it working and, unfortunately, do not have time to create a repro.
Sorry, for the trouble
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
33 | |
21 | |
16 | |
8 | |
7 | |
6 | |
5 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.