Hey Jared,
This is - how it is, but...
A good way to deal with this issue is to keep the package names generic (non-manufacturer and non-quantity centric) so that they apply to many combinations of things. The package description can be modified without causing you to add a new package to the database. Populate the package with you most popular products that meet the solution described in the Package Name.
Example:
Package Name:
Room Package - Distributed A/V - In-Ceiling - Speakers and Source Control
Package Description:
In-ceiling speakers and source control
++++++++++++++++++++++++++++
In the above example, you can change the description to include quantities and other information like manufacturers, or specific features.
This will change the description only in the one instance of the package in the project.
Keeps you from having lots of different packages.
+++++++++++++++++++++++++++++
Example of a Project Modified Package, name is the same, but with an embellished description!
Package Name:
Room Package - Distributed A/V - In-Ceiling - Speakers and Source Control
Package Description:
4 Phat 8" In-ceiling speakers and color touchpanel source control with totally ultra killer graphix uzer inta-face designed by Andy Warhol and Killa' mo-dee.
__________________
Kevin Mikelonis
Process Dealer Services Group
D-Tools Certified Partner
PO Box 3443
Paso Robles, Ca
805.275.2308
www.processdsg.com
info@processdsg.com
Stuff That Works
|