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.