Resistors - Values Sorted by ID

Warning:  

Updating a design from a library with changed Primary Keys (ID) will ruin your day.

Part IDs of any parts that have been placed into your designs should NOT renumbered.

Using this tip is only recommended when new libraries are being created

Steps for Creating Resistor Values Sorted by ID:

Components Panel > Display All Columns

Sorted in Components Panel

Copy and Paste to Excel, Renumber ID

Parts > Import Excel

Warning:  

Updating a design from a library with changed Primary Keys (ID) will ruin your day.

You should not renumber Parts IDs of any parts that have been placed into your designs. 

This trick is only recommended when creating new libraries.

Done !

Altium Database Library Basics

Components are created from Parametric Data, Symbols and Footprints.

DBLib Example: 

Capacitor with one Symbol and three Footprints for an 0402 (1005 Metric)

DBLib and SVNDBLib libraries use database structures like Access or MySQL to store parametric data and library file paths (file pointers).

For portability reasons and simplicity relative file paths to Symbols and Footprints may be used when the *.DBLib file is stored in the same parent folder.

Example:

click on image to view

For collaboration and version control each Symbol and Footprint should be stored in a single library file. 

Single part files are also required for version controlled libraries, i.e. SchLib and PcbLib files. 

Database Libraries use file paths Footprint Ref, Footprint Ref 2, Footprint Ref 3.

The current (default) footprint is the Footprint Ref specified in the database.

Remove all Linked Footprints from all *.SchLib files.

All footprints (models) need to be deleted from *.SchLib files to avoid missing footprints.

When parts have matched Library Ref and *.SchLib names and all *.SchLib are stored in the same Symbols folder you can be confident that no duplicate Lib Refs exist in your library.

When parts have matched Footprint Ref and *.PCBLib file names and all *.PCBLib are stored in the same Footprints folder you can be confident that no duplicate Footprints exist in your library.

Recommendation . . .

Select Parts > Configuration > Enforce Matching Filenames and Library References.

Invalid Characters in File Names (Windows)

  < (less than)
  > (greater than)
  : (colon - sometimes works, but is actually NTFS Alternate Data Streams)
  " (double quote)
  / (forward slash)
  \ (backslash)
  | (vertical bar or pipe)
  ? (question mark)
  * (asterisk)

Reserved File Names (Windows)

CON, PRN, AUX, NUL 
COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9
LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9

Value Parameter:

A user parameter named Value can be used to simplify displaying the value of a Resistor, Capacitor, Inductor or a component's part number.

Primary Key:

Using a simple incremented number for the Design ID will simplify updating libraries and projects with part number choices.

Duplicate Parts:

Good library management tools include checks for duplicate part numbers.

Summary:

Good libraries have consistent symbols and footprints (same graphic symbols) are used for common Resistors, Capacitors and Inductors.

Before migrating libraries to Altium's Managed Component Libraries, it's highly recommended that the library be scrubbed (cleaned).

Parts is a Library Management Tool that can be used to create clean Database Libraries.

That's it !

Migrating Parts to Altium's Managed Components

 Link to YouTube Video

Tip1: 

LifeCycle is a reserved field name in Altium's Managed Components Database. 

If you are migrating a database library to Altium's Managed Components you can rename the LifeCycle field to Parts_Status.  Part_Status is the Default filed name in the latest version.

The Parts Frontend is compatible with LifeCycle or Parts_Status. 

As of Mar 26, 2022 the default was field name in the Parts Database changed to Part_Status to simplify migration to Altium's Managed Components.

Tip 2:

Before migrating to A365 edit the Altium DBLib. Uncheck Queries created in Access or Views created in MySQL to prevent duplicate component errors during migration.

Queries and Views are records in the Parts table that were filtered by Part_Type.

That's it !