Help - Build 1310 professional I don't have a menu to transfer eap file to feap!

[Richard Freggi]

This is crazy.  All columns failing the JOIN are related to custom tagged values I added to the UML types before the transfer to feap.
If I remove the column alias statement on my query (select columname AS displayname) then the query runs but the JOIN fails to filter any rows (blank result)
I can see some garbage characters with umlaut in the raw column names if I SELECT * from t_objectproperties

Weird stuff.  Fortunately I am not using these tagged values yet, so will just delete and recreate them.

Ps.s. Geert thanks for your advice, tried it did not help in this case, seems to be the garbage tagged value names that cause the errors (mismatch of column names in the query causing ADOB error)

[Richard Freggi]

All fixed now, thanks everyone for practical and moral support!

A final issue I had to resolve was that Firebird was really picky with my Memo fields and would fail some sting concatenation operations (||).  I tried casting Note fields to VARCHAR, TRIM and everything else, but I only SUBSTRING can force Memo fields to work reliably with ||.  So I had to set all memo string manipulation to 

 || SUBSTRING((Note field blah blah) FROM 1 FOR CHAR_LENGTH(Note field )-1)  ||

After dropping the final character in the note, the note displays in full, so there must have been some garbage ASCII in the last byte, many possible causes - maybe the transfer to Firebird, or the fact I have pasted into the Notes from different languages so double byte may have screwed something up.

Anyways I'm happy as!  Thanks everyone.

[RoyC]

There might also have been a T missing from CONSTRAINT in LIKE ('%IMPLEMENTATION CONSTRAIN%')))

But you seem to have fixed the problem anyway.