• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. PCB Design
  3. Configuring CIS with MS Access using ODBC mapped to Unix...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 165
  • Views 14513
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Configuring CIS with MS Access using ODBC mapped to Unix (UNC) Disks in Windows 10...

UlfK
UlfK over 8 years ago

I have an issue with Windows 10 and ODBC...

It seems that Microsoft has disabled the possibility to map the ODBC driver configuration to an Access database residing on a UNC mapped disk.

We have a Solaris system with SAMBA software that maintains our group areas. According to IT service dept, this set-up is the only one that facilitates a flexible way to set disk quotas and rights in our organization. Previous Windows 7-installation had not have any problems with the CIS database on a UNC-mapped drive, but Windows 10 is a different story. The ODBC canvas refuses to see a network drive that uses UNC. It is not possible to browse for it. It is not possible to map it using text entry. Allegro has no problem finding footprints, and Capture can find the schematic library. CIS does not work.

I am not the only one that has discovered this, and there seem to be a circumvention by editing the registry (Regedit.exe) and define the paths/disk from there, but I have not found any information that is directly applicable to MS Access, .MDB and Capture CIS configuration.

My choice to use Access was based on that it is included in Microsoft Office and that it was adequately convenient to use it as a front end tool when adding part entries. I could consider changing to some other database system, but then the library needs to be converted...

I have logged a support case with Cadence and also with our IT support. In the mean time, my thread is both a comment and a question if others have seen this, or if anyone here has information how to resolve the issue.

  • Cancel
Parents
  • oldmouldy
    oldmouldy over 8 years ago

    Then this is indeed an issue with Windows 10 and ODBC configuration and in no way related to how Capture CIS, or any other ODBC application, makes use of ODBC capabilities. For fairly obvious reasons, applications that use ODBC have no idea what the database "beyond" the ODBC driver is, the driver makes "any" database appear to have the same capabilities to the application, so, if you cannot configure the database through the ODBC control panel, any ODBC application won't be able to use it. In turn, Microsoft have been actively moving users away from multi-user sharing of "file based" data, like Excel and Access, for about 15 years or more, providing SQL Server Express and migration tools to move to a "network based” database. Excel and Access would still work fine for "personal" data, local to your machine but, if you want the data remote, to be shared, you need to move to a "network based" database like SQL Server, MySQL and so on. If required, you can still manage these databases through Access and the ODBC connection to them. This concerns data in your Access database and would not affect any libraries used by the tools.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • UlfK
    UlfK over 8 years ago in reply to oldmouldy

    I see...

    Then: Where to find information about a suitable system using what you/Microsoft suggest? I invoked the ODBC control panel in order to see if I could connect to some (not yet defined) SQL service

    that uses networks but I guess that my knowledge is quite limited. Nowhere could I see any method of browsing to the UNC-defined network resources.

    It would be interesting to talk to some Cadence Application Engr who should know how to address the issue.

    Thanks for the information. Much appreciated.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • oldmouldy
    oldmouldy over 8 years ago in reply to UlfK

    Windows 10 isn't going to make an ODBC connection to a remote file. You either need you Access file local to your machine, or get a network based, SQL database setup, which would mean installing the database application on a remote machine, migrating the data to it, and configuring the ODBC connection for it. Since you have an IT service department, they should be able to help you in selecting a suitable database, machine to run it on, and migrating the data.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • oldmouldy
    oldmouldy over 8 years ago in reply to UlfK

    Windows 10 isn't going to make an ODBC connection to a remote file. You either need you Access file local to your machine, or get a network based, SQL database setup, which would mean installing the database application on a remote machine, migrating the data to it, and configuring the ODBC connection for it. Since you have an IT service department, they should be able to help you in selecting a suitable database, machine to run it on, and migrating the data.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information