Minor ODBC weirdness

[MarAndreas]

I just packaged an application that requires a System DSN.

For some reason, I couldn't get the natively installed application to see the DSN - it looks OK in ODBC Admin, it just doesn't work.

I suspect a 32bit vs 64bit issue, but I haven't been able to nail it down yet.

I did, however, find a workaround:

Using the cmd.exe debug entry point to launch odbcad32 in the virtual environment, I could create a DSN useable by the packaged application.

Added it to the package through smbmerge, rebuilt, and I have a working Thinapp.

Weird.

[Cievo]

I think you can look into sandbox after creating ODBC and look for those changes in original project folder.

[MarAndreas]

Thank you, that helped

The path in the virtual registry is identical to the path in the physical registry - but the virtual registry has no Wow6432Node

Used the *other* odbcad32 (in syswow64) to create the DSN

Now the native installation is also working properly.