Stats

  • State Not Answered
  • Replies 7
  • Subscribers 44
  • Views 6697
  • Members are here 0
More Content

Microsoft Office 2019 "Click2Run" No ODBC-Drivers for Access .MDB-files - Advice how to move forward?

UlfK

Having installed  Office 2019 after a computer upgrade I discovered that I could not configure an ODBC 64 bit data source for our Access .MDB database used for CaptureCIS. After some searching, the answer was that Microsoft does not provide the possibility to add ODBC drivers for .MDB in an Office 2019 Installation "Click to Run". The only possible drivers are in principle "SQLite 3". Previously, I had to overcome the problem with ODBC configuration on SAMBA mapped drives that Microsoft did not allow using its GUI. The mapping had to be defined in the Registry editor. All was well until I hit this one today... An easy way would be to convert to Excel but there is no driver for that format either.

Since Access can export to SQL-format (at least according to the export menus) I think that the only possible way forward is in that direction.

But can the Cadence software 17.2 and 17.4 connect the CIS to such databases?

Is there any easy enough front end for SQLite 3 that does not require a lot of hardware and software resources?

Comments invited.

  • 0 in reply to steve

    While we enjoy the full set of Cadence design features (High speed options, Sigrity etc.), we have no grants for parts that are considered "business" such as CIP or a license for the Library builder. The CIP is a"would be very nice to have" but I don't think the cost is justifyable. Anyway, your hint was an eye-opener to what is out there.

  • 0 in reply to UlfK

    I downloaded  Paralell Systems Appnote. The Wizard and management version(s) described in that document seems to have been replaced by later versions of the Microsoft SQL-Server management tools including the Migration utility. I had to install an old version of MS Office that provided support for Access .MDB, Then  the latest versions of SQL-Server Express with SQL Management tools and also localize the Windows installation to US/English with proper notation for commas and interpunctuation, since the translation process trowed a "Culture not supported" Error Message. After a few attempts which included manual configuration of the SQL agents/network/firewall settings, I could translate the .MDB file and also have a look at the translated result in the Management tool.

Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.