Hello

The following works just fine as a stand alone SQL in EDBManager...

INSERT INTO MaaArc SELECT * FROM Maa
WHERE (MaaID = 5185);

.. but when I create a stored procedure with the following, it fails to do anything.

PROCEDURE "PROC1" (IN "E_ID" INTEGER)
BEGIN  
EXECUTE IMMEDIATE 'INSERT INTO MaaArc
                   SELECT * FROM Maa
                   WHERE (MaaID = ? );' USING E_ID;
END

The parameters window opens, I type in 5185 and click on Ok, but no error message, & no data.

What could be wrong?

Regards & TIA

Peter

Peter


You've fallen into the same trap someone else did recently. EXECUTE IMMEDIATE does not return a result, it just does what you've asked it to do. So first question is have you looked at the table to see if its been updated?

Roy Lambert [Team Elevate]

Roy

Sorry, the 'no data' reference was ambiguous. Yes, I checked the table, and the record was not inserted.

I reckon that the problem is in my use of the parameter.

Regards

Peter

Roy

It would help if I operated the parameters window properly - I hadn't added the 5185 that I typed in, so it was passed the default NULL.

Sorry to waste your time, it is working as advertised now

Regards

Peter

Peter

>It would help if I operated the parameters window properly - I hadn't added the 5185 that I typed in, so it was passed the default NULL.

The number of times I have done that is legion. My favourite is to type in the parameter, think I have clicked the button (my Dell notepad's mouse pad is temperamental) and then put the next one in only to find the query doesn't work.

Roy Lambert [Team Elevate]

Roy,

<< The number of times I have done that is legion. My favourite is to type
in the parameter, think I have clicked the button (my Dell notepad's mouse
pad is temperamental) and then put the next one in only to find the query
doesn't work. >>

I do the same thing , and I'm wondering if an <Enter> button to save would
be helpful for the way that I've coded the entry of the params.  What do you
think ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>I do the same thing , and I'm wondering if an <Enter> button to save would
>be helpful for the way that I've coded the entry of the params. What do you
>think ?

What a brilliant concept. Go for it!

Roy Lambert

Tim,

> I do the same thing , and I'm wondering if an <Enter> button to save
> would be helpful for the way that I've coded the entry of the params.  
> What do you think ?

Absolutely!

Uli

Roy,

<< What a brilliant concept. Go for it! >>

Hah ! I don't hear that word often in relation to one of my ideas.

I also added the up/down key functionality, so when you're sitting in the
edit, you can move from param to param without losing focus on the edit, so
you can pretty much keep your hands off the mouse unless you need to NULL a
param.

--
Tim Young
Elevate Software
www.elevatesoft.com

Uli,

For your information:

1) The build 18 EDB Manager has an option for using Tahoma for the font.

2) That old Locate issue with partial-length searches on characters whose
comparison result changes depending on which characters come after the
partial-length characters has been fixed finally.  I finally figured out
that just stepping down to a linear (as opposed to binary) search of the
index pages in such cases will solve the problem.  What triggers it is a
non-ANSI/Unicode collation for the last char/varchar column for the
partial-length search, which is specific enough that it only affects very
few cases, and you probably won't notice that it is using a linear search
instead of a binary search of the index pages.  We have a Hungarian customer
that ran into the same issue as you did with the German collation and
partial-length Locates, and the solution finally came to me.

--
Tim Young
Elevate Software
www.elevatesoft.com