• 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. Allegro X Capture CIS
  3. Suitable Front-End for SQL-Migrated Capture-CIS Database...

Stats

  • State Not Answered
  • Replies 3
  • Subscribers 44
  • Views 10023
  • Members are here 0
More Content

Suitable Front-End for SQL-Migrated Capture-CIS Database?

UlfK
UlfK over 4 years ago

Having successfully converted our Microsoft Access ( .MDB) database to SQL-format and used the database in the Capture-CIS environment for schematic instantiation, the nest question is: How to find a simple "Front-End" Interface that provides the same functionality as the  Microsoft Access User interface. (Office 2016 and 2019) Yes - I have tried it also with the SQL-database but it converts the database into some form that seems to corrupt it.

I also tried converting the database into SQLite-format using a free trial conversion tool found on the internet. That worked too.  (Had to manually strip the tools added non-sense extra column).

In both cases, Developer tools was used to manipulate and add entries in the SQL-Database but developer tools are not my first choice.

Are there any reasonable low-cost (or preferably) free front end that provides simple enough functionality?

  • Cancel
  • Sign in to reply
  • oldmouldy
    0 oldmouldy over 4 years ago

    You can use Microsoft Access to maintain data in a database based on Microsoft SQL Server but not change the database structure, like add Tables and so on. Create a "blank" database, then use the External Data options and Link the Access database to the SQL Server database for maintenance of the database fields via the ODBC setup. If you go down the SQLite route, which probably won't be quite so handy in a multi-user scenario, you can find tools like SQLiteStudio, SQLite Management Studio and SQLite Tools, and others, from a web search.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • RFinley
    0 RFinley over 4 years ago

    Stick with MS-SQL or Postgres.  MS SQL Server Management Studio, included with MS-SQL, does far more than I've ever need. 

    If you have less than 10gb of data, the license is free.

    For your front-end question:  Orcad CIP (component information protocol) is a very good value.   

    Built-in BOM/WhereUsed functionality and with a web interface, populate new part records directly from distributor web data and text searches.  Automatic stock level update query from distributors. 

    Then we use OpenBom for system-level and inventory.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • UlfK
    0 UlfK over 4 years ago in reply to RFinley

    Yepp - I have tried MS SQL-Server. No problems with database size. Only a few Gigabytes. Nowhere near the "Cost Threshold". I also had a look at CIP. Very neat but there are no free lunches and cost is an issue. In the past I have had problems with footprints downloaded or generated from US-sources. As far as I know, the US procedure is that the manufacturing takes care of solder mask "swell" as the footprints have equal copper and solder mask sizes. In Europe, the mask is defined during the footprint creation process. Older PCB CAD-system had a function for solder mask "swell" during Gerber creation I have not seen this in Allegro.

    My co-workers do not do PCB CAD on a daily basis. Hence, the procedures must be as easy to follow as possible. Access ".MDB" was OK.

    As Oldmouldy suggested, I did try External Data option, but I must have made something wrong. It must be possible to add and edit records without messing things up. Will try again! 

    OpenBom is another thing I have not explored.

    Thanks for your suggestions.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
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