Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations cowski on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

PDMWorkgroup, Drawing property not reading Model property placed in Mo 2

Status
Not open for further replies.

Standing

Mechanical
Jan 14, 2002
1,578
Text in drawing title block is updating by using $PRPSHEET:"Description". The property called Description is not updating in drawing from the model. I am using a note with “Link to Property” in my template. Is there a setting I am missing somewhere or is an API required?

My end result is to have PDM read the Description from the model and put the Description in the PDM drawing description text box automatically. See attached.


Bradley
SolidWorks Pro 2008 x64 SP3.0EV
PDMWorks Workgroup, Dell XPS Intel(R) Pentium(R) D CPU
3.00 GHz, 5 GB RAM, Virtual memory 12577 MB, nVidia 3400
e-mail is Lotus Notes
 
Replies continue below

Recommended for you

The associatively that you desire is currently not available. See: thread559-203488 and thread559-138421 for more details and a link to a macro for copying properties (non associative). I encourage you to put in an enhancement request as this has been inquired about frequently.

Eric
 
Eric,
I put in an enhancement request. Thank you for working on a holiday, our VAR is off today. A star for you. I will not work on the macro.

Bradley
SolidWorks Pro 2008 x64 SP3.0EV
PDMWorks Workgroup, Dell XPS Intel(R) Pentium(R) D CPU
3.00 GHz, 5 GB RAM, Virtual memory 12577 MB, nVidia 3400
e-mail is Lotus Notes
 
I just did a bunch of programming experiments using SW Doc Manager and other objects to see if there was a way around this exact issue. No luck.
 
I've been barking about this for years, and also submitted ER's numerous times. Hopefully Bradley's will get though to SW this time.

Colin Fitzpatrick (aka Macduff)
Mechanical Designer
Solidworks 2007 SP 5.0
Dell 490 XP Pro SP 2
Xeon CPU 3.00 GHz 3.00 GB of RAM
nVida Quadro FX 3450 512 MB
I'm just a little verklempt. Talk amongst yourselves. I'll give you a topic. Pink Floyd, was neither Pink nor Floyd. Discuss!--“Coffee Talk” Mike Myers SNL
 
What can be deceptive is that in a macro, the property will fully resolve if drawing and part are both open in SW. Now way to resolve if one or both are not open.
 
I like the program that Eric wrote to sync properties, but I cannot figure out how to run his swp macro from a Visual Basic exe program. It is easy to run an exe from swp but not the other way around. Does anyone now how to run a swp macro from a Visual Basic exe program?

Here is a ling to a macro that he wrote a while back for this purpose.


Bradley
SolidWorks Pro 2008 x64 SP3.0EV
PDMWorks Workgroup, Dell XPS Intel(R) Pentium(R) D CPU
3.00 GHz, 5 GB RAM, Virtual memory 12577 MB, nVidia 3400
e-mail is Lotus Notes
 
I believe you can just turn the .swp into a .bas and then open it with VB.NET and compile, so the macro becomes the .exe (of course, with some editing). A .swp file is a .bas, so all you need to do to convert it is to rename the file name from *.swp to *.bas. Easy stuff. Hope this helps point you in the right direction.

Matt Lorono
CAD Engineer/ECN Analyst
Silicon Valley, CA
Lorono's SolidWorks Resources
Co-moderator of Solidworks Yahoo! Group
and Mechnical.Engineering Yahoo! Group
 
I don't think .swp = .bas. .swp can encompass multiple modules and forms.

However... you can export any module or form from a macro. Right-click the module in the part where modules and forms are listed and select "Export". Then you have a module that can be brought into VB.

Forms exported from SW macros show up as "Designers" modules when imported to VB6. Not sure why, I think it's because the actual form is not the same object type as used by VB6. They still work pretty much the same.
 
Assuming what you are saying is true, if it is a simple one module macro, simply renaming .swp to a .bas and in reverse is the conversation method.

The .swp could be more complex, yes. I haven't done this in awhile, but I don't remember having any issues with it regardless of complexity. Something to try out, for sure.

Matt Lorono
CAD Engineer/ECN Analyst
Silicon Valley, CA
Lorono's SolidWorks Resources
Co-moderator of Solidworks Yahoo! Group
and Mechnical.Engineering Yahoo! Group
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor