Sebastien FLAESCH wrote: > This looks for sure like an unixODBC bug. Yes, it would seem so. Please report this to the unixODBC folks. If you're right, I'm sure you'll find them very interested in correcting it. Regards, --jkl