Re: Access frontal interface for Oracle database
From: Gloops <gloops_at_invalid.zailes.org>
Date: Mon, 11 Aug 2008 07:24:46 +0200
Message-ID: <g7oieu$k9h$1@aioe.org>
>
> It could in the past and I don't see why it can't now.
> As 'execute' is a sql*plus keyword, and not a SQL keyword,
> the syntax is { BEGIN <procedure>; END; }
>
> (from memory)
>
OK thanks, I shall try BEGIN, although the ODBC error message box answered me that the only recocknized keywords were INSERT, DELETE and UPDATE (and perhaps one more, that was on Friday).
Date: Mon, 11 Aug 2008 07:24:46 +0200
Message-ID: <g7oieu$k9h$1@aioe.org>
sybrandb_at_hccnet.nl a écrit, le 11/08/2008 00:18 :
> On Sun, 10 Aug 2008 16:06:41 +0200, Gloops <gloops_at_invalid.zailes.org>
> wrote:
>
>> The Execute method (of ADODB ? not sure I remember, I have a look >> tomorrow) can execute, on Oracle, commands INSERT, DELETE, UPDATE, but >> not EXECUTE, I could not execute a stored procedure in Oracle that way.
>
> It could in the past and I don't see why it can't now.
> As 'execute' is a sql*plus keyword, and not a SQL keyword,
> the syntax is { BEGIN <procedure>; END; }
>
> (from memory)
>
OK thanks, I shall try BEGIN, although the ODBC error message box answered me that the only recocknized keywords were INSERT, DELETE and UPDATE (and perhaps one more, that was on Friday).
I hope you do not mix up, as BEGIN is a key word that begins the code of an Oracle procedure.
In SQL*Plus, I launch the stored procedure by typing EXECUTE followed by the name of the procedure -this is why I tried this from Access.
So, I am going to type BEGIN instead, that is not expansive after all :) I tell you that tonight. Received on Mon Aug 11 2008 - 00:24:46 CDT