![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi! I'd like to prepare all my statements before I start collecting data. However, ExecuteSQL and CreateSLQ both run the statement as soon as they are called. Is there any way to create a statement without executing it? Lots of Greetings! Volker I usually wrap them in a procedure and the first time they are called they |
#3
| |||
| |||
|
|
"Volker Hetzer" <volker.hetzer (AT) ieee (DOT) org> wrote in message news:do9c6c$5fu$1 (AT) nntp (DOT) fujitsu-siemens.com... I'd like to prepare all my statements before I start collecting data. However, ExecuteSQL and CreateSLQ both run the statement as soon as they are called. Is there any way to create a statement without executing it? I usually wrap them in a procedure and the first time they are called they run and thereafter I call the refresh method. Yes, but I wanted to get rid of that this-is-my-first-call stuff... |
#4
| |||
| |||
|
|
Jim Kennedy wrote: "Volker Hetzer" <volker.hetzer (AT) ieee (DOT) org> wrote in message news:do9c6c$5fu$1 (AT) nntp (DOT) fujitsu-siemens.com... I'd like to prepare all my statements before I start collecting data. However, ExecuteSQL and CreateSLQ both run the statement as soon as they are called. Is there any way to create a statement without executing it? I usually wrap them in a procedure and the first time they are called they run and thereafter I call the refresh method. Yes, but I wanted to get rid of that this-is-my-first-call stuff... But it looks like I'm stuck with it. Lots of thanks nevertheless. Volker You could search for something that can't exist. It will do the query, but |
#5
| |||
| |||
|
|
"Volker Hetzer" <volker.hetzer (AT) ieee (DOT) org> wrote in message news:dobfo4$ebh$1 (AT) nntp (DOT) fujitsu-siemens.com... Jim Kennedy wrote: "Volker Hetzer" <volker.hetzer (AT) ieee (DOT) org> wrote in message news:do9c6c$5fu$1 (AT) nntp (DOT) fujitsu-siemens.com... I'd like to prepare all my statements before I start collecting data. However, ExecuteSQL and CreateSLQ both run the statement as soon as they are called. Is there any way to create a statement without executing it? I usually wrap them in a procedure and the first time they are called they run and thereafter I call the refresh method. Yes, but I wanted to get rid of that this-is-my-first-call stuff... But it looks like I'm stuck with it. Lots of thanks nevertheless. Volker You could search for something that can't exist. It will do the query, but not return any rows. My statements were inserts. |
![]() |
| Thread Tools | |
| Display Modes | |
| |