Reserved Error -7711 Pass Thru Query

[David]

I can run this SQL fine in SQL Developer (run script) and export it to a text
file. I would like to be able to execute this query in Access 2003. I
believe rule_text is a CLOB field.

When I add this SQL in a pass thru query I get the Reserved Error (-7711)
error.

select trim(replace(rule_text,';',chr(10))) as "content"
from table_rule
where table_rule.operation = 'DISPATCH'


Any help is much appreciated.

David

 

[Bob Barrows]

I can run this SQL fine in SQL Developer (run script) and export it
to a text file. I would like to be able to execute this query in
Access 2003. I believe rule_text is a CLOB field.

When I add this SQL in a pass thru query I get the Reserved Error
(-7711) error.

select trim(replace(rule_text,';',chr(10))) as "content"
from table_rule
where table_rule.operation = 'DISPATCH'

I don't know what backend database you are using so all I could do was
resort to google. Do any of these results help?
http://www.google.com/search?source...GGLD:2003-36,GGLD:en&q=Reserved+Error+(-7711)

 

[KARL DEWEY]

I think you will need .... , chr(13) & chr(10))) as "content"

 

[Bob Barrows]

I can run this SQL fine in SQL Developer (run script) and export it
to a text file. I would like to be able to execute this query in
Access 2003. I believe rule_text is a CLOB field.

When I add this SQL in a pass thru query I get the Reserved Error
(-7711) error.

select trim(replace(rule_text,';',chr(10))) as "content"
from table_rule
where table_rule.operation = 'DISPATCH'

Perhaps an explicit cast to CHAR or VARCHAR?

 

[David]

Bob,
Not sure how to do that. This is SQL in a pass thru query. Googling
explicit cast vba, i saw where I can explicitly define the data type in the
DIM statement in code, but not sure how to do it in a pass thru query.

 

[Bob Barrows]

Um, it's a passthru query. VBA is irrelevant. You would need to read the
documentation for the database that you are passing the query to and use
whatever casting or conversion functions are offered by the sql dialect used
by that database to do the explicit cast or conversion. In other words, it's
got to be something you can run in "SQL Developer" assuming that is the
native query development tool for that database.

This is assuming the datatype is the problem, of course ...