I need to create an assembly consisting of up to 150 spheres
of varying sizes, all filled with varying liquids, all contained
within a larger sphere. The volume of this larger surrounding
sphere is also filled with liquid. The catch is that the customer
wants to be able to vary the XYZ coordinates, inside and outside
diameter, and filling liquid of every smaller sphere, as well as
delete spheres that are not needed. The filling liquid in the
surrounding sphere must "flow" into any areas not occupied by
smaller spheres. The customer wants to use a pre-existing Excel
table, with the required data on many different tabs, to drive the
design parameters. We're currently running SW07 with Excel 03, so
the 256 columns rules out a DT at this time. We're soon upgrading
to SW08, and could purchase Excel 07 to gain the additional
columns, but I'm concerned that the table will be unmanageable, or
require a large amount of embedded excel code to change the
presence of spheres within the filling liquid, as well as correct
for any blank lines in the driving excel table if the customer
decides to have only 100 smaller spheres for example.

So the question is this: Go the upgraded design table route and back-correct for any number of spheres less than 150, or outsource for an API (we don't have the skills in-house) that can take the driving tables and simply generate the assembly correctly from the front end?

The final users will need a relatively intuitive and straight forward interface, knowing basically nothing of SW.

Also, we may in the future need to add other shapes, such as wedges, plates, and support structures for the a prototype version of the real sphere assembly, so flexibility with add-ons would be nice.

Any and all help would be greatly appreciated.

So the question is this: Go the upgraded design table route and back-correct for any number of spheres less than 150, or outsource for an API (we don't have the skills in-house) that can take the driving tables and simply generate the assembly correctly from the front end?

The final users will need a relatively intuitive and straight forward interface, knowing basically nothing of SW.

Also, we may in the future need to add other shapes, such as wedges, plates, and support structures for the a prototype version of the real sphere assembly, so flexibility with add-ons would be nice.

Any and all help would be greatly appreciated.

WT