Wow that's a lot of work. Normally I suggest that you run work station setup, run MAS once and then use Windows Explorer and delete the MAS90 folder on the workstation and any desktop icon.

I sure understand that, after my detective work on this yesterday, for sure!

I do have one question, however. One of the pressing reasons for me to figure this out, but which I did not include in my post, was that the company CFO needs to retain access to the old server via his existing v4.0 workstation because it contains several old companies which they did not want to migrate to v4.5 on the new (terminal) server at this point (maybe later). It will not be in conflict with v4.5 on the terminal server, but how would I go about installing 4.5 on his workstation, as you suggest, so he can get just the ODBC driver (which is all he needs of v4.5 on his workstation)? Would that not conflict with the existing 4.0?

It comes down to this: he needs both his existing 4.0 workstation as well as the 4.5 ODBC driver on his workstation. Maybe it is a faulty assumption on my part that there would be a conflict if I were to install 4.5 on the same workstation.

Just a bit more explanation on why I went to all the pains to figure out a solution.

Being not a MAS90 specialist, but a systems administrator responsible for the broader picture of ensuring the overall health and orderliness of both servers and workstations, I have often found two things when users remove a program folder manually without a proper uninstallation of the application:

1. It leaves a host of orphaned registry entries and files on the hard drive that could interfere with subsequent installations of the product or simply appear as files of unknown risk when later attempting to clean up the system or identify a virus.
2. Subsequent uninsallations of the applications will probably fail because the uninstall information was in the folder that was manually removed.

Besides this, I find the message regarding ODBC connections failing IF the registry entries are removed somewhat misleading, since these fail even if one selects "No" at that prompt. That just made me too curious to leave this alone, so will note that about 90% of my original post was the process of getting there.

In the end, the solution was simple: copy two DLLs to System32 and double-click a .reg file to insert a few relevant registry entries. I am just a bit surprised there is no "install just the ODBC driver" option inside the workstation setup process, given how easy it would be to do it, or at least some other post here having the process I discovered through trial-and-error. All is good now, though (I think).

Your issue is that you want to run multiple installs from one desk top. That's really simple. I have 4.05, 4.10, 4.20, 4.30, 4.40 and 4.50 installed on my computer at home and run each as I need them with no issue. If he can get to the old install they just do the work station install for v.450 and give it a different name so you have two icons on your desktop and your fine.

Thank you. As I indicated, I am not a MAS90 specialist, so I am not used to programs that will allow multiple versions. Most applications I support either upgrade prior versions or conflict with them when installed.

Still, determining the actual requirements of the standalon ODBC driver was a good exercies for me--and I am just geeky enough to actually enjoy the process of figuring out registry entries, etc.

Hello, I just wanted to add my experience with this. I did get it to work via the explanation above, although my steps were a little different because I'm on a 64 bit machine. For some reason, even though the ODBC drivers themselves are 32-bit, they sit in the SysWOW64 folder, not the System32 folder. So, here are the steps I followed to get this to work.

1. Copy pvxio.dll and pvxodbc.dll into C:\Windows\SysWOW64 on the target machine (You should be able to find them on another machine in the same folder)

2. Run a registry edit something like this (be sure to replace the serial number with yours. Again, you should be able to find this from another machine)

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sage Software\ProvideX ODBC Driver]
"Serial"="###############"
"Name"="Registered MAS 90 & MAS 200 user"
"Company"="Sage Software, Inc."
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\MAS 90 4.0 ODBC Driver]
"Driver"="C:\\Windows\\SysWOW64\\PVXODBC.DLL"
"Setup"="C:\\Windows\\SysWOW64\\PVXODBC.DLL"
"SQLLevel"="0"
"DriverODBCVer"="03.00"
"APILevel"="1"
"ConnectFunctions"="YYN"
"FileUsage"="1"
"UsageCount"="dword:0000000"
"CPTimeout"="<not pooled>"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\ODBC Drivers]
"MAS 90 4.0 ODBC Driver"="Installed"

3. Re-add the odbc connection with this driver manually through the ODBC administrator. Copy values from existing ODBC connection on another machine. 

If you get an error like this:
The setup routines for the MAS 90 4.0 ODBC Driver ODBC driver could not be loaded due to system error code 126: The specified module could not be found. (C:\Windows\SysWOW64\PVXODBC.DLL).

...then you need to make sure you have a file called msvcr100.dll in your SysWOW64 folder. If you don't, copy it from another machine. I believe this is installed as part of C++ redistributable installs. 

A little late to the party but I just wanted to suggest instead of trying to use the Sage 100 Workstation install, just install the ODBC driver from ProvideX.  You can find downloads for it here http://www.pvxplus.com/pgsrvr.pvp?pg=dl_optional

If you have problems getting it to recognize a license, you might actually have to do the workstation install, uninstall leaving the registry keys, and then do the ODBC install.  I have had very good luck with it though.

Also wanted to point out that on a 64-bit machine, all the 32-bit files are actually in the SYSWOW64 folder, while the files in system32 are the 64-bit.  Doesn't make a lot of sense, but that's what they did.