Ken Boardman

Using Design Tables with VBA Macros

Discussion created by Ken Boardman on Mar 31, 2008
Latest reply on Apr 8, 2008 by Luke Malpass
Goal:

Is to use an embedded Excel Design table in a Part or Assembly file to automatically "read" the embodying filename (ie of the Part or Assembly) then split it into pre-defined custom parameters (may need some VBA for this...) representing fields that need to automatically update and populate a drawing title panel etc.

Our current filename convention is as follows;

nnn_xxxx_yyy_A##_description

Where nnn = the product (ie project) number allocated at the start of the project.
xxxx = identifier (Incremental number unique to each part)
yyy = Document Type Descriptor, number: See below
· 100 for mechanical drawings
· 110 for mechanical assemblies
· 111 for PWA's
· 200 for schematics
· 500 for artworks
A = version (letter), used to capture fit, form or function changes used in Part, Assembly and Drawing documents
## = revision numbers, eg 01, 02, 03 etc (used for drawing files only)

The main problem we face is that we have not been able to "extract" the complete filename inside the embedded Excel Design Table to feed into the associated internal VBA scripts for string operations to split them into individual parameters. (The AIM: is to set a custom parameter say "PartNumber" = nnn_xxxx_yyy , "Version" = A, "Revision" = ##, and "Description" = description , we will probably also need to find a way to increment and store the various Version and Revision numbers along with an ECR number and Change Note, ChangedByUser and ChangedDate ... to track each change through the components lifecycle...in say an automated Revision table...)

Ideally we would like to have our start parts and assemblies contain the embedded Design Table and as the file is given a name the spreadsheet would "instantaneously" update the fields in the design table so they would automatically propagate into the drawing title panel fields and also be available later for use with PDM if/when we update to it.

Regards,

Ken

Outcomes