How did I miss that other thread? It answers what I was asking. Just make it clear up front which parts must be fitted as spec'ed, which can be substituted with approval, and which are not critical (this will obviously depend on how much you trust your CM). Internal part numbers and pick lists can be a good way to go if you need to maintain part sourcing flexibility but can't necessarily rely on someone else to source acceptable alternates, but it may be easier to talk to your assembly house about alternate parts-they may already have suitable parts on hand or may get substantially different pricing than you do, so you may get better pricing if you let them know which specs are critical and let them shop around for you. I think you might be able to do similar things with Vaults, but I've never used them. If you use a dbLib, you add a separate entry for each part number to the database, and link in the same footprint/symbols from those library files, so you're effectively generating however many different values you need parametrically. It also makes it easier to specify an EXACT part number where that's critical versus other places where there's some flexibility. Adding a separate part to the library for each value requires more work up front, but makes for easier outputs and consistency control later on. If you are using the library at a large organisation or university, check that your IT allows connections out on TCP port 1433 (MS SQL) - many will need to make an exception for you.Manually editing parameters would require the least setup upfront, but would be a tremendous pain to maintain.If you are a home or small office user, check that your router allows connections out on TCP port 1433.
Check that Windows Firewall allows Altium access to the internet.There is an issue stopping Altium from connecting to the database server. If instead, you see the message "Connection Failed. For Altium Designer 18 and newer: Download and install MSSQL Native Client 64 Bit.For Altium Designer 17 and older: Download and install MSSQL Native Client 32 Bit.Installing Microsoft Access will not fix the error. Open the DbLib that you downloaded from the portal, if the error message mentions requiring 64-bit Microsoft Access - you do not need to install Microsoft access. Alternatively, you may be displayed the connection error below and not be able to view the components panel items at all. If you are looking at the components panel and can see different categories/views, but you cannot see any components in any view, you may have a connection error.
0 kommentar(er)
