Can you let me know your exact Direct Oracle Access version?
If you are using a multi-byte character set database, then it might help if you set TOracleSession.BytesPerCharacter to bcAutoDetect.
The upcoming 4.0 release supports Timestamps as a TDateTimeField in a dataset, so this conversion error can no longer occur in this situation.
------------------
Marco Kalter
Allround Automations