ODBC Crystal Reports (Crystal Corral) for Vista 6.1 (no Rich-Text V

Yahoo Archive
1
I have an RDS (Windows 2008 R2) server installed with vista 6.1 client installed as an app. Vista performs fine.

My problem is Crystal Reports. We have a multitude of reports that have been developed for day to day use. I have spent a good deal of time trying to configure ODBC to jive so that I can run these reports.

When I run C:\windows\syswow64\odbcad32.exe I can see the drivers that I pointed to by running a .reg file.
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432\ODBC\ODBCINST.INI\MERANT 3.60 32-BIT Progress SQL92 v9.1D]
"APILevel"="1"
"ConnectFunctions"="YYN"
"CPTimeout"="60"
"Driver"="V:\\prgs91d\\bin\\PGPRO915.DLL"
"DriverODBCVer"="3.60"
"FileUsage"="0"
"Setup"="V:\\prgs91d\\bin\\PGPRO915S.DLL"
"SQLLevel"="0"
"UsageCount"="1"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432\ODBC\ODBCINST.INI\PROGRESS 9.1D DB2 Driver]
"APILevel"="1"
"ConnectFunctions"="YYY"
"CPTimeout"="60"
"Driver"="V:\\prgs91d\\bin\\p1udb16.dll"
"DriverODBCVer"="3.70"
"FileUsage"="0"
"Setup"="V:\\prgs91d\\bin\\p1udb16s.dll"
"SQLLevel"="1"
"UsageCount"="1"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432\ODBC\ODBCINST.INI\PROGRESS 9.1D Informix Driver]
"APILevel"="1"
"ConnectFunctions"="YYY"
"CPTimeout"="60"
"Driver"="V:\\prgs91d\\bin\\p1inf16.dll"
"DriverODBCVer"="3.70"
"FileUsage"="0"
"Setup"="V:\\prgs91d\\bin\\p1inf16s.dll"
"SQLLevel"="1"
"UsageCount"="1"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432\ODBC\ODBCINST.INI\PROGRESS 9.1D SQL Server Driver]
"APILevel"="1"
"ConnectFunctions"="YYY"
"CPTimeout"="60"
"Driver"="V:\\prgs91d\\bin\\p1msss16.dll"
"DriverODBCVer"="3.70"
"FileUsage"="0"
"Setup"="V:\\prgs91d\\bin\\p1msss16s.dll"
"SQLLevel"="1"
"UsageCount"="1"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432\ODBC\ODBCINST.INI\PROGRESS 9.1D SQL Server6 Driver]
"APILevel"="1"
"ConnectFunctions"="YYY"
"CPTimeout"="60"
"Driver"="V:\\prgs91d\\bin\\p1ss616.dll"
"DriverODBCVer"="3.70"
"FileUsage"="0"
"Setup"="V:\\prgs91d\\bin\\p1ss616s.dll"
"SQLLevel"="1"
"UsageCount"="1"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432\ODBC\ODBCINST.INI\PROGRESS 9.1D Sybase Driver]
"APILevel"="1"
"ConnectFunctions"="YYY"
"CPTimeout"="60"
"Driver"="V:\\prgs91d\\bin\\p1ase16.dll"
"DriverODBCVer"="3.70"
"FileUsage"="0"
"Setup"="V:\\prgs91d\\bin\\p1ase16s.dll"
"SQLLevel"="0"
"UsageCount"="1"

In addition, I have added what I believe to be the appropriate registry entries for 64x systems as well to my scripted reg file for ODBC

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\Progress91D]
"Driver"="V:\\prgs91d\\bin\\PGPRO915.DLL"
"Description"="Vista 6.1"
"HostName"="epicor.premedtec.local"
"PortNumber"="6150"
"DatabaseName"="mfgsys"
"LogonID"="sysprogress"
"StaticCursorLongColBuffLen"="4096"
"DefaultIsolationLevel"="READ UNCOMMITTED"
"ArraySize"="50"
"DefaultLongDataBuffLen"="2048"
"UserID"="sysprogress"
"Password"="sysprogress"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432\ODBC\ODBC.INI\Progress91D]
"Driver"="V:\\prgs91d\\bin\\PGPRO915.DLL"
"Description"="Vista 6.1"
"HostName"="epicor.premedtec.local"
"PortNumber"="6150"
"DatabaseName"="mfgsys"
"LogonID"="sysprogress"
"StaticCursorLongColBuffLen"="4096"
"DefaultIsolationLevel"="READ UNCOMMITTED"
"ArraySize"="50"
"DefaultLongDataBuffLen"="2048"
"UserID"="sysprogress"
"Password"="sysprogress"

But I still get the same problem with connecting. Has anyone successfully troubleshot this issue? What steps am I missing?