Thread View: borland.public.cppbuilder.database.dbexpress
1 messages
1 total messages
Started by Remy Lebeau (TeamB)
Tue, 22 Jul 2008 20:19
TSQLStoredProc - ftString parameter does not work with SQL Server 2005
Author: Remy Lebeau (TeamB)
Date: Tue, 22 Jul 2008 20:19
Date: Tue, 22 Jul 2008 20:19
23 lines
1973 bytes
1973 bytes
I have a stored procedure in SQL Server 2005 that has 3 parameters - 2 nvarchar(64) parameters and 1 int parameter. Internally, the procedure builds up an XML string (for inserting elements into an existing schema collection). I configured TSQLStoredProc to hold two ftString and one ftInteger TParam objects. If I try to run the stored procedure using TSQLStoredProc, SQL Server fails with an "illegal xml character" error. Even weirder, the error reports a character index that is inside a standard XML tag with valid characters in it. I am assigning plain Ansi strings to the TParam::Value property. No MBCS involved. However, if I run the same stored procedure via TSQLQuery using an "EXECUTE" SQL statement, everything works fine. Does an ftString TParam work correctly with SQL Server 2005? I tried ftWideString, but then I get an "unsupported type" error from SQL Server when executing the procedure. Gambit
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads