Hi,
No, I edited the config file in response to an PostgreSQL error indicating that the insert failed as a result of the 9 character date field. (Recall date field contained 'anonymous'. Don't know why the server didn't truncate - is that something that I may have affected in a different configuration file?
For the purpose of demonstration I moved on to the dbaseIII backend, but this wouldn't be acceptable for larger scale use of the product going forward.
I've considered that if I couldn't find any other way around this problem I could always develop a BEFORE INSERT trigger to take care of it...but I really don't want to do this unless I have to.
Where might truncation be invoked (or not) in the server? I'll go back and have another look at the code...