>>IMO, DE is pretty good. The only thing which should be checked is
>>DE.Cursor.Database (CursorSource for free tables) properties. They carry values
>>(mappings) from development machine, so they should be reset programmatically
>>in DE.BeforeOpenTables event.
>
>Never thought of that... the way I always handle this is to make sure I have the PATH set to the data directory, and that works for me to keep relative references in the DE....

Yes, usually it's sufficient, but if in some rare case you will get two duplicate data sets with one on the same path as it preserved in DE and you actually assume to use another one, then you get in troubles. I mean that few lines in DE.BeforeOpenTables event can save from getting crazy here.