Sure SQLSetEnvAttr() is missing but it's far from the only function. Before that it was SQLAllocHandle() and I'm sure there will be more after SQLSetEnvAttr(). Backwards compatibility is a big task for a small gain, given how many v2 drivers are around today. The general point is that this should be driven by the needs of real applications. Could you ask this user to get a +odbc trace from current wine-staging? I'll see if I can make that Jet driver work.