Subject The same, but different...
Author Aage Johansen
You know the situation: it works on my pc, but not on the
customer's. Or, it works on my copy of the database, but not on the
customer's.

I have a form with a TIB_Grid and a TIB_SearchEdit. The table is simple:
create table PRODUCTION_COMPANY (
ID integer not null primary key,
PROD_COMP varchar(40),
LAND varchar(3)
);
commit;
and the script creating the table also inserts a few records:
insert into PRODUCTION_COMPANY (PROD_COMP,LAND) values
('Metro-Goldwyn-Mayer','USA');
insert into PRODUCTION_COMPANY (PROD_COMP,LAND) values ('Selznick
International Pictures','USA');
insert into PRODUCTION_COMPANY (PROD_COMP,LAND) values ('Loews Inc','USA');
commit;
A trigger takes care of the ID-field. Also, some more records have
been inserted.

Now, on my computer everything works as expected. I see all records
in the grid, and everything is fine. When I direct my program to the
customer's database (just changing the server:database info) I cannot
see any records in the grid. However, we can see matching records
when using the TIB_SearchEdit. Clearing the text in the
TIB_SearchEdit leaves us again with an empty grid.
This happens also when run at the customer's site.

There are some indexes and a ForeignKey thingy, but this shouldn't
make any difference.
alter table PRODUCTION_COMPANIES
add constraint FK_PRODUCTIONCOMPS2
foreign key (PRODCOMP_ID) references PRODUCTION_COMPANY (ID)
on update cascade;

I remember having some difficulty getting everything to work properly
- maybe I re-entered the records in the table. But it is the same
program and the tables look pretty much the same in both databases
(same metadata, some records are different).


Sorry for rambling on and on, but I'm out of ideas.


--
Aage J.