We have a situation with one workstation (no other workstations have this issue but they are all Windows 7) on the network (Win 10).

Very "simply" when we try to setup a System DSN on this workstation we get as far as picking out one of the global files. As soon as we pick it out the ODBC Administrator crashes. If we attempt to do this at one of the other workstations there is no issue in picking out the global file and all is good.

We have double checked with their IT people that it is not a "rights" issue as this workstation and login to the server has full read write access and this is proven by the fact that all the other modules work correctly and can do anything with these other modules.

The client in question uses ODBC V9.2A with the latest date stamp.

We are not sure what it is.

Any suggestions are appreciated.

John:

32 bit versus 64.

Your Windows 10 w/s is 64 bit and you are using the 32 bit ODBC administrator.

It sounds like you have "*" in the Table Selection field. There are too many tables in a typical Adagio setup for ODBC to handle. Choose a single table to load, such as AR92ACST for that AR Customer master.

Only load tables you need to use in the ODBC connection.

The Data Dictionary Exporter will give you the ODBC names of all the tables used in Adagio.

ODBC DSN needs to be setup with Run as Administrator. If the database is on a mapped drive and the Administrator user doesn't have the mapped drive setup, it will not find it.

When there is an issue with the mapped drive, I usually create a small batch to map the drive with Net Use and run the batch as Administrator.