🚀 go-pugleaf

aleplgr wrote:
>
> But the stored procedure needs the table to be ordered in a
> particular order.

The stored proc can select it with an Order By.

> SELECT * FROM TEMP1 ORDERED BY COL1  AS TEMP
> because my procedure needs the table ordered

The *physical* order of records in a table is never guaranteed in a 
relational SQL database (unless it specifically supports what are called 
"cluster" indexes, which InterBase does not support). So even though your 
select includes an Order By, the records will be inserted in whatever 
physical order is most convenient for the server. In order to see records in 
a particular order you must select them in that order *at the point where 
you want to view or process them*, not at the point of inserting them.

> I should order the table before starting to work with it in the
> procedure and I don't know how to ORDER it and give it a name..

You don't have to give it a name, you just need to select them in the order 
you want, so in the stored procedure you need to do this:

FOR
  SELECT FLD1, FLD2, FLD3 [,...] FROM TEMP1
  ORDER BY COL1
  INTO :FLD1, :FLD2, :FLD3 [,...]
DO BEGIN
  // do whatever processing you need here
END;

You need to define local variables for the fields, e.g. in the above sample, 
that might be:

DECLARE VARIABLE FLD1 INTEGER;
DECLARE VARIABLE FLD2 VARCHAR(20);
DECLARE VARIABLE FLD3 DATE;

-- 
Wayne Niddery - Winwright, Inc (www.winwright.ca)
"The two most abundant elements in the universe are hydrogen and
stupidity." - Harlan Ellison