In the meantime for testing you can modify your copy of ADSPROF in D:\Softrak\data\Company1

Don't copy ADSPROF when you refresh the data.

You need to discuss with the site's Adagio consultant, I would be very surprised to hear that they installed Adagio on each workstation and not a single install on the Server.

Workstation installs would be needed on the workstations.

Ya, they were having performance issues on the server so they went with workstation installs.

Oh, I meant to ask what the EZTasks file is all about?

It seems that the tasks are causing the issue. of course the current location cannot be changed and somehow I need to get ODBC to play nicely with the eztasks file.

As mentioned before it doesn't seem to care about the currency file it only freaks out when using the proper eztasks file.

What role does eztasks play in the ODBC? There might be some special config with the client that is causing problems. I was warned that there was some oddities. The eztasks might be one of them.

Adagio is licensed to be installed on one computer, that computer may be a Server when multiple users are running the applications.

The setup you describe is not stable in a multiuser environment.

As I said, I am very surprised that an Adagio consultant would have taken this approach.

Understood. At some point that will need to be addressed. What is the reason to believe that my problem will go away if I install the ODBC in the same directory as the other modules when I am able to connect to the company by pointing to a different tasks folder.

I would like to understand the how the tasks folder is affecting the ODBC connection so I can make the appropriate changes to my import / setup or suggest an appropriate fix to the client.

The EZTASKS entry in ADSPROF is really a pointer to the system files ( not to a single file ) that control data access, multi user access, and record and file locking. The files in the folder pointed to by this entry ( and in the subfolders) are codependent on each other.

In your incorrect setup you load system files from D:\Softrak\System and then point to a different set of files.

Are all the files in C:\Softrak\System identical to D:\Softrak\System?

My guess would be that they are not.

So the module will need to be installed in the same folder to ensure proper data access / record and file locking. That makes sense. The error indicated a failure to connect which was probably a failure to correctly establish a lock.