Still no joy on this. I think it may be using a different version of the OLE driver for ODBC as It works for a collegue with an older version of this driver. Maybe VB.NET is not using this driver at all and is using something else