Yes… it can be tricky though. Some settings are different depending on whether you are 32/64 bit.
Can you make an ODBC connection on if you are logged directly to the server?
I usually get that working first.
And then for client PCs, I usually start by running Netsetup… then tweak things as needed.
\ServerName\epicor\oe101c\netsetup\setup.exe
There are some answerbooks on the old EpicWeb that will get you in the neighborhood.
And let us know if you are still having trouble.
Also… you may get errors connecting to some tables… (“too many indexes…” I think)
The WorkArounds2 reg entry fixes those.
Here is a sample for V8… last line… it would be the same for E9
Windows Registry Editor Version 5.00
I used ODBC with Progress (OE 10.1b It think) back when we were on V8.
Does the ODBC connection setup on the computer pass the connection test?
There’s a chance you might need to run the ODBC32 setup on the client machine, instead of the 64 bit ODBC.
The 32 bit ODBC is at C:\Windows\SysWOW64\odbcad32.exe
There were also some “fixes” that we had to do. It involved creating a few registry entries. Here’s the contents of a REG file we used to run on clients so they could use ODBC connections to the V8 server.
usdataps00108 is the name of the V8 server that Progress resided on.
The “WorkArounds2”=“40960” is the fix we needed to manually enter.
Duplicate the entries in [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\MC_MfgSys] with updated name and Port setings for connections to other DB’s. For example:
[HKEY…ODBC.INI\MC_PilotComp]
“Description”=“Pilot Company”
“PortNumber”=“8380”
all other entries are the same as those in [HKEY…MC_MfgSys]
and add "MC_PilotComp"="OpenEdge 10.1B driver"
to the [HKEY...\ODBC Data Sources] section