Thanks for the cursorchema creating script. I will try it.
Btw the same effect can be achieved using DISPLAY STRUCTURE TO FILE command.

>"This is really weird. Is the only way to fix this to check every numeric field in every record at upsize time, as Fabio suggests?"
>
>it depends, are these values valid? if so you have to make the postgres column wider, otherwise you probably should find a way that these invalid values aren't stored in the dbf in the first place. I always tackle problems from their source, and if these values aren't valid the problem is that they are somehow getting stored. If you solve it like this you don't have to deal with these kind of consecutive faults.

Christian,

I want allow customers to upsize large amounts of existing data. This data contains illegal (out of range) numeric fields values which I do'nt want to store in Postgres database. I need to skip or blank those fields.