locating design table path with vb code api's
locating design table path with vb code api's
(OP)
i'm using v5r12 sp6
i routinely do the following with mouse clicks (i.e. interfacing via the gui): say that i've got some catpart file open and it uses an excel design table file, and my catia options are set so that my spec tree shows the design table icon (usually down in relations), so that i can right-click properties over this design-table icon in the spec tree and it will pop up a window showing me the path to THAT particular design table.......and that's how i discover where that excel file exists on my hardrive.....
question: how do i do the same thing but with vb ? what are the api's that my vb prog should be calling in order to retrieve that info (=the path of the xcel file) ?
thanks so much for any help or suggestions that one might give .... maris
i routinely do the following with mouse clicks (i.e. interfacing via the gui): say that i've got some catpart file open and it uses an excel design table file, and my catia options are set so that my spec tree shows the design table icon (usually down in relations), so that i can right-click properties over this design-table icon in the spec tree and it will pop up a window showing me the path to THAT particular design table.......and that's how i discover where that excel file exists on my hardrive.....
question: how do i do the same thing but with vb ? what are the api's that my vb prog should be calling in order to retrieve that info (=the path of the xcel file) ?
thanks so much for any help or suggestions that one might give .... maris





RE: locating design table path with vb code api's
it was straightforward, actually,,,,i seemed to have missed it the first time around....
just declare a designtable viz,
dim dt as DesignTable
then hook it into some relavent relations object e.g.,
set dt = partdoc.part.relations.item("DesignTable.1")
then grab the info that i want (the xcel path name) viz,
msgbox dt.FilePath
i should have seen this before i posted this question, sorry..