sql - How to avoid ODBC parameterization for the question mark character ? within literals and comments? -
Am I running on an issue where my question marks are characters? 'There is a problem within my SQL script within the comments when I run these status through an ODBC connection using the Visual FoxPro SQLEXEC function, then seen these letters as prompts for parameters and VFP values going.
What are my options for handling question marks when SQLEXEC? I'm hoping how I can be certain how to turn off parameterization or alternatively avoid some of these letters before passing them as commands. So far, I have not found any evidence of this kind of solution, it seems that I may have to get all the comments tab which is undesirable because they generally make statements for stored procedures and we want to keep these comments safe. . I am hoping that there can be a more soothing solution to completely remove any comment.
It appears that it may be that the question mark characters in the SQL command when facing the comments Is there no relation? Usually represent the parameters in the ODBC and in the same way as in VFP.
Just a warning - the VFP parser will catch any question mark in the SQL string, even if it is a SQL commentary (i.e. with a line start - or / * * / / between the bracket ) And if there is nothing that can be a variable out there will be an error if it can be a variable, but you do not define it on runtime, you get an ugly input box to enter it . Even worse, your user receives it.
Then look. - Dragon Nedelzhkovich
Comments
Post a Comment