Yes, your friend has it correct. I just made another change to my template above for the ACEODBC.DLL path after "Program Files" it could be different depending on which version of MS Access your running. See the "MyDLLPath" string above.
Original Message:
Sent: 02-19-2024 15:03
From: Jeff Schwenk
Subject: Crystal 2020 No Longer Includes MS Access, Excel, or Text Connectors
Asking for a friend - If you make the appropriate changes to the above, can you then save it as TXT file, then change the extension to REG, then right click, run as administrator so that Windows will load it?
Again, asking for a "friend"
------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444
------------------------------
Original Message:
Sent: 02-19-2024 02:17
From: Dan Burleson
Subject: Crystal 2020 No Longer Includes MS Access, Excel, or Text Connectors
I figured out how to avoid having to visit each workstation to setup a User DSN and instead add a System DSN for 64-Bit Crystal 2020. I looked into the Registry to see why adding an entry for an Access database to the System panel would be accepted, but not be reflected in the System panel nor in ODBC sources visible to Excel or Crystal. It turns out that the entries for the MS Access database are being added in an odd place. Normally, System DSN's are stored under:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI
However, now they are being stored under:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\ODBC\ODBC.INI
This might explain why the DSN isn't visible in the System panel after successfully setting one up. I was able to create a similar registry entry that, when loaded to the normal area, worked as expected and was visible in the System Panel. As always, make a registry backup before using the template below. It must be loaded from a local and not a network drive or you will get a file error. Adjust all the strings the begin with "My" for your target installation. Note that this is for 64-Bit Office.
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\MyAccessDSNName]"Driver"="C:\\Program Files\\Common Files\\Microsoft Shared\\OFFICE16\\ACEODBC.DLL""DBQ"="\\MyServer\\MyPath\\MyAccessDatabaseFileName""Description"="MyAccessDatabaseDescription""DriverId"=dword:00000019"FIL"="MS Access;""SafeTransactions"=dword:00000000"UID"=""[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources]"MyAccessDSNName"="Microsoft Access Driver (*.mdb, *.accdb)"[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources]"MyAccessDSNName"="Microsoft Access Driver (*.mdb, *.accdb)"[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\MyAccessDSNName\Engines][HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\MyAccessDSNName\Engines\Jet]"ImplicitCommitSync"="""MaxBufferSize"=dword:00000800"PageTimeout"=dword:00000005"Threads"=dword:00000003"UserCommitSync"="Yes"
------------------------------
Dan Burleson
Software Consultant
Connex Software
Corvallis OR
541-224-6642
Original Message:
Sent: 02-09-2024 01:15
From: Dan Burleson
Subject: Crystal 2020 No Longer Includes MS Access, Excel, or Text Connectors
Yes, you'll have to visit each workstation that uses the custom report. The drivers come with windows, but without the built-in connector, adding a DSN and referencing it in the Crystal report will work. Here's a sample of the registry entry import to quickly add a DSN (replace the entries between << & >> with your specific names and paths). You can save this as a file with a ".reg" extension and run it with administrator privileges or to reduce the chances of a typo, create your own DSN manually and export the relevant registry entries.
Windows Registry Editor Version 5.00[HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI\<<My Access Database DSN name>>]"Driver"="C:\\Program Files\\Common Files\\Microsoft Shared\\OFFICE16\\ACEODBC.DLL""DBQ"="\\\\<<My Server>>\\<<My Path>>\\<<My Access Database file name>>""Description"="<<My Access Database Description>>""DriverId"=dword:00000019"FIL"="MS Access;""SafeTransactions"=dword:00000000"UID"=""[HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI\<<My Access Database DSN name>>\Engines][HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI\<<My Access Database DSN name>>\Engines\Jet]"ImplicitCommitSync"="""MaxBufferSize"=dword:00000800"PageTimeout"=dword:00000005"Threads"=dword:00000003"UserCommitSync"="Yes"
------------------------------
Dan Burleson
Software Consultant
Connex Software
Corvallis OR
541-224-6642
Original Message:
Sent: 02-08-2024 16:20
From: Jeff Schwenk
Subject: Crystal 2020 No Longer Includes MS Access, Excel, or Text Connectors
What is the impact if we run a Crystal report from the Sage menu that pulls data from an Access DB located on the server? Do we still need to install these drivers at the workstation level?
------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444
Original Message:
Sent: 01-15-2024 07:38
From: Jeff Schwenk
Subject: Crystal 2020 No Longer Includes MS Access, Excel, or Text Connectors
Please raise the issue/question at MOTM.
------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444
Original Message:
Sent: 12-08-2023 19:02
From: Jeff Schwenk
Subject: Crystal 2020 No Longer Includes MS Access, Excel, or Text Connectors
What??? Sage is trying to save money by leaving out helpful features??? Perish the thought!!!!
------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444
Original Message:
Sent: 12-08-2023 17:28
From: Todd Martin
Subject: Crystal 2020 No Longer Includes MS Access, Excel, or Text Connectors
Last time I saw Crystal Reports not have specific drivers were due to the OEM relationship with Sage and Crystal. They removed them on purpose and a lot of us complained about it and the following version had them back in there. Maybe this is the same that has come back around.
------------------------------
Todd Martin
MBA Business Software
https://www.mbabsi.com