Database fields for components with multiple footprints and symbols

[Analog]

I use Altium Symbol libraries to store my component parameters. I’m am considering using Access database to better manage my components and enter/store parameters. This would give me extra flexibility and hopefully result in cleaner libraries.

I sometimes use alternative symbols and often use different footprints for the same component. Sometimes the footprints are just L-N-M variants and sometimes special silk designs.

If I use a database to manage the parameters, do I make a field for each symbol and footprint?

[ajb]

There's a set of field format for multiple PCB footprints:

Footprint Ref → [Footprint Ref]
Footprint Path → [Footprint Path]
Footprint Ref n → [Footprint Ref n]
Footprint Path n → [Footprint Path n]

The documentation says "Unlimited footprint model references (and paths)", but I haven't pushed my luck.  Having a lot of database fields gets cumbersome anyways.

I don't think you can do the same thing for schematic symbols.  I think the only way to get different symbols for the same library part is to use the alternate graphical modes, which have to be defined in the schematic lib, and are kind of hidden in the component properties.

[Analog]

Thanks for the reply. I don't know why I thought there was some other way of dealing with multiple footprint and symbols. I think I'll just stick to 3 footprints and try out the alt view to see if it still works OK with external references.

[Tabs]

not sure if its too late or what version of AD you're on but AD18 will office 64bit if you want to use DBLibs. AD < 18 needs 32bit office.
Microsoft don't recommend have both versions installed, but Altium advises a work around for those that cant install 64bit.
if you have a subscription office365 then you can uninstall the 32bit version and install 64bit.
Not sure what that will do to your existing 32bit access database library. This is what stopped me upgrading to AD18 because office 64bit wont work with some of the legacy tools our IT use.
One to watch out for.

[ddavidebor]

not sure if its too late or what version of AD you're on but AD18 will office 64bit if you want to use DBLibs. AD < 18 needs 32bit office.
Microsoft don't recommend have both versions installed, but Altium advises a work around for those that cant install 64bit.
if you have a subscription office365 then you can uninstall the 32bit version and install 64bit.
Not sure what that will do to your existing 32bit access database library. This is what stopped me upgrading to AD18 because office 64bit wont work with some of the legacy tools our IT use.
One to watch out for.

You can if you have that sort of issues use Microsoft SQL server express (it's free) and move the access database over with a wizard microsoft provide provides.
If you access it only from you machine there is i think almost no configuration.

[warpco]

So... How can I assign multiple footprints to a component in a database library? What does this mean?

Footprint Ref → [Footprint Ref]
Footprint Path → [Footprint Path]
Footprint Ref n → [Footprint Ref n]
Footprint Path n → [Footprint Path n]

Do I need to create multiple columns in a DB table and name them "Footprint Ref 1", "Footprint Ref 2", etc? What if one component has five footprint variants, and others only one? Leave these additional cells blank for all the components except one?

People say that database libraries in Altium Designer are superior to integrated, but with all their quirks, I doubt it is true.

[ddavidebor]

Do I need to create multiple columns in a DB table and name them "Footprint Ref 1", "Footprint Ref 2", etc?

Yes

What if one component has five footprint variants, and others only one? Leave these additional cells blank for all the components except one?

Yes, you need to leave those cell NULL, which is different from a cell with an empty string.

People say that database libraries in Altium Designer are superior to integrated, but with all their quirks, I doubt it is true.

The Intlibs are also pretty quirky and harder to manage.