I am using MS Access with postgresODBC and I'm not sure which of both is responsible for the following behaviour. However I did not experience this behaviour in the past with MS SQL Server. I could ...