I get the above error when I assign a value to the "laname" parameter in the following procedure:

PROCEDURE "CreatePlanLandApps" (IN "pid" INTEGER, "laname" VARCHAR(100), "wid" INTEGER)
BEGIN
 DECLARE LandAppsCursor SENSITIVE CURSOR FOR LandAppsStmt;
 PREPARE LandAppsStmt FROM 'SELECT * FROM PlanLandApps';
 OPEN LandAppsCursor;
 START TRANSACTION ON TABLES PlanLandApps;
 BEGIN
   INSERT INTO LandAppsCursor VALUES (Null, pid, laname, 0, wid);
   COMMIT;
   EXCEPTION ROLLBACK;
 END;
END

The assignment comes from the text string in a text edit control:

ParamByName('laname').AsString := frmNewLandApp.edtLandAppName.Text;

Any suggestions?

Thanks

Peter

Duh. I'll answer my own question. The field order was wrong. This does raise a small question about the order in which manager displays fields in
an open table (this is where I took my order from). This does not necessarily reflect the underlying field order of the table. Is there a way to
ensure that it does?

Peter,

<< Duh. I'll answer my own question. The field order was wrong. This does
raise a small question about the order in which manager displays fields in
an open table (this is where I took my order from). This does not
necessarily reflect the underlying field order of the table. Is there a way
to ensure that it does? >>

If you're referring to the table grid display, then just right-click on the
headers for the columns, and then select the Reset Columns option.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote:

<< If you're referring to the table grid display, then just right-click on the
headers for the columns, and then select the Reset Columns option.  >>

That's the one - thanks Tim.

--
Tim Young
Elevate Software
www.elevatesoft.com