If only one bitness of driver is registered, you can only manage the DSN with the correct bitness of odbcad32. That means, for example, you can create a 32-bit User DSN with the 32-bit odbcad32 then manage it with the 64-bit odbcad32. If both a 32-bit and a 64-bit version of an ODBC driver are registered with the same driver name (which is what SQLAnywhere does if you install both drivers), Microsoft treats them as equivalent except, of course, for bitness. There's some Microsoft Magic behind the scenes too. It is very important always to use a fully qualified, absolute path to the DLL that you want to register or unregister. Regsvr32 nowadays will automatically reinvoke the correct bitness of itself to match the DLL that you are registering. ![]() I have a few things to add to what Justin posted but the size & formatting constraints on comments are annoying.
0 Comments
Leave a Reply. |