When ChronoScan connects to a database through ODBC or OLE DB (lookups, value lists, the ODBC export module, the external data panel) the drivers must match the bitness of the ChronoScan installation: a 32-bit ChronoScan can only use 32-bit drivers and DSNs, and the 64-bit ChronoScan can only use 64-bit ones.
ODBC Data Source Administrator: on 64-bit Windows there are two of them. For 32-bit ChronoScan use C:\Windows\SysWOW64\odbcad32.exe; for 64-bit ChronoScan use the standard one (C:\Windows\System32\odbcad32.exe). A DSN created with the wrong one is not visible to ChronoScan.
Access and Excel files: they need the Microsoft Access Database Engine (ACE) of the same bitness. The 64-bit ChronoScan installer includes the 64-bit engine; for 32-bit ChronoScan download the 32-bit engine from Microsoft Access Database Engine 2010 Redistributable.
Microsoft Office conflict: Windows only allows one bitness of the Access Database Engine to be installed through the normal setup, and Microsoft Office installs its own. If Office is 32-bit and you need the 64-bit engine (or the other way round), install the engine with the /passive option of its installer, or use the 2007 engine, which can coexist. See Microsoft KB 2269468.
SQL Server: use the Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) or the native SQL Server OLE DB provider; both are available in 32-bit and 64-bit.
Connections are created in the Administration tab, Databases panel, Database connections, and stored as .udl files in the DataConnections folder of the configuration.
