Re: Using SQL CONNECT problem to MS SQL database

Darryl,

It's a long shot but, what happens if you use dynamic SQL statements?

With dynamic SQL you create your statement as a string and then do a:
Exec SQL immediate :sql_string ;

Regards,
Luis

Regards,

Luis

Sent from my Moto G phone. Please excuse my brevity.

On Aug 25, 2016 8:59 AM, "Darryl Freinkel" <dhfreinkel@xxxxxxxxx> wrote:

The problem is not MS SQL.
The problem is the LPEX editor and RPG compiler.
I need a way to tell the editor that the SQL validation must be done using
the RDBdire.

On Thu, Aug 25, 2016 at 8:56 AM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

You might try putting square brackets around the table name - if that
doesn't work, ask your MS SQL folks what the bracketing characters are.

HTH
Vern

On 8/25/2016 7:49 AM, Darryl Freinkel wrote:

Using STRSQL, the following statement works.

select symbol from AXTRN01..UNITOFMEASURE

but in the RDi I cannot do this.

Exec Sql Select count(*)
into :Count
from AXTRN01..UNITOFMEASURE
where Symbol = trim(:pUOM);

The double dot is required in MS SQL. Does anyone know of a way around
this
issue?

TIA

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
Darryl Freinkel
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.