I tried the AsString. It made no difference. No special character
sets are involved.

I can replace the stored procedure with a query and the query will
work in Dialect 3 when the stored procedure intended to accomplish
the same task will fail.

I have tried many things but the stored procedures that operate on
TABLE CONTACTTEMP fail in Dialect 3 and work in Dialect 1. Stored
procdeures operating on other tables seemed to work in both Dialects.
I tried dropping the table and stsored procedures and recreating
them. The results were the same. Dialect 1 works and Dialect 3 fails.
The meta data for TABLE CONTACTTEMP is below.


CREATE TABLE CONTACTTEMP (
ID INTEGER NOT NULL,
EMPID CHAR (6) NOT NULL,
LABELCOMPLETE VARCHAR (80),
SALUTATIONCOMPLETE VARCHAR (80),
ORG VARCHAR (80),
ADDR1 VARCHAR (60),
ADDR2 VARCHAR (60),
ADDR3 VARCHAR (60),
CITY VARCHAR (40),
ST_ABRV ST_ABRV,
ZIP CHAR (10),
JOBTITLE CHAR (50),
CONTACTLASTFIRST VARCHAR (35),
PHONE CHAR (13),
PHONEEXT CHAR (4),
FAX CHAR (13),
ADDRRESSTYPE SMALLINT,
CONTACTID INTEGER,
ORGCODE VARCHAR (20));

--- In IBObjects@y..., Geoff Worboys <geoff@t...> wrote:
> The problem gets more interesting ;-)
>
> Where you have...
>
> ParamByName('EMPLOYEE').Value := gsEmpID;
>
> can you try
>
> ParamByName('EMPLOYEE').AsString := gsEmpID;
>
> (I am presuming gsEmpID is a string value.)
> I have an inate distrust of Delphi variant types, and the .Value
> property uses variants.
>
>