Text and number as Param

[dupe]

We have a problem with params in our SQL.
If we define an SQL statement with a param like:

SELECT * FROM Test WHERE Column = :1Param

SDAC only shows the "1" as param but not the whole "1Param".
We used ADO before and it hadn't this problem.
Do you have any ideas what we could do?

In TParser.InternalGetNext you distinguish between numbers and alphas.
There is a routine called "IsAlpha" and "IsNumber".
Is there a reason for this?

Best regards

[dupe]

We have a problem with quoted params too.

SELECT * FROM TEST WHERE Column = :'A A'

In this case we dont even have a param.

[AlexP]

Hello,

To use such parameter names, you should quote them with square brackets

Code: Select all

SELECT * FROM Test WHERE Column = :[1Param]

[dupe]

In our program the users have the opportunity to write their own statements.
And because it's in use for many years now there are over thousands of none quoted parameters.
So we can't force them to quote their's.
Why is there such a behavior?
Is there a possibility to get the old ADO behavior?

[ViktorV]

We will consider the possibility to implement this functionality in one of the next SDAC versions.