J
Jacques
Hi there,
I'm facing quite a weird thing with an ADP file (backend is SQL server
2000).
Among the various stored procedures I have, just some of them can be
executed from the database window (by double-clicking it).
The others give various error message, depending of the parameters
structure I have. Possible error messages are:
-ADO-fout: Line1: Incorrect syntax near ')'. Must declare the variable
'@P1'. Statement(s) could not be prepared.
-ADO-fout: Line1: Incorrect syntax near ','. Must declare the variable
'@P1'. Statement(s) could not be prepared.
-ADO-fout: Column or parameter #1: Cannot find data type OUTPUT.
Parameter '@P1' has an invalid data type. Statement(s) could not be
prepared.
When trying to EDIT them in design mode, it gives me the same error
message!!!
The strange thing is that it perfectly works on other clients, using
the same ADP file and the same SQL database. The list of references is
the same too. I suspected different versions of the ADO 2.1 library
but had not a chance to check this yet (I doubt it has something to do
with this).
Can it be related to the fact that the client has local admin
permissions or something?
I can't see what makes these SP look different (that is, those which
work vs those which does not).
I'm totally lost! Would be great if you could help.
Thanks,
Jacques.-
I'm facing quite a weird thing with an ADP file (backend is SQL server
2000).
Among the various stored procedures I have, just some of them can be
executed from the database window (by double-clicking it).
The others give various error message, depending of the parameters
structure I have. Possible error messages are:
-ADO-fout: Line1: Incorrect syntax near ')'. Must declare the variable
'@P1'. Statement(s) could not be prepared.
-ADO-fout: Line1: Incorrect syntax near ','. Must declare the variable
'@P1'. Statement(s) could not be prepared.
-ADO-fout: Column or parameter #1: Cannot find data type OUTPUT.
Parameter '@P1' has an invalid data type. Statement(s) could not be
prepared.
When trying to EDIT them in design mode, it gives me the same error
message!!!
The strange thing is that it perfectly works on other clients, using
the same ADP file and the same SQL database. The list of references is
the same too. I suspected different versions of the ADO 2.1 library
but had not a chance to check this yet (I doubt it has something to do
with this).
Can it be related to the fact that the client has local admin
permissions or something?
I can't see what makes these SP look different (that is, those which
work vs those which does not).
I'm totally lost! Would be great if you could help.
Thanks,
Jacques.-