You may check on which Service Pack and Hotfix level is installed on each user's PC. Our VAR once instructed me that a lot of the functionality that is used by the 3DX connection is actually contained in the code for the V5 Service Packs and Hotfixes. The functionality does change between...
In this macro, you're creating a new parameter regardless of whether a parameter with the same name exists or not. Better would be to incorporate a logic check. If the parameter exists, then use it, or else create the new parameter.
As far as I am aware, what you request is not directly possible in the program architecture. Here are a few possible alternative methods. Unfortunately they all involve creating additional files.
Copy the reference part model and make unique parts, and edit each as needed. This might be useful...
As you've seen, the output reports the scale as a multiplier, and not as ratio as we commonly write. The way I solved this was to make a series of conditions. It's been long enough I forgot how, but I think I used a select case routine. I mapped out all the common scales that I considered...
This is still a great question, and at my company, our thinking and methodology have advanced a bit compared to the last post. Our current methodology for this sort of thing is to include an attribute on the Product that is the part or item number in the MRP system. Then (manually) apply the...
To the question about prevention: In my company we have done a few things to prevent this problem from occurring. (Yes, I've been bit by it also)
1) Launch your program with unique shortcuts and environments for each customer. This unique environment also includes a unique background image for...
Should be this (now that I'm back in front of my screen):
Tools > Options > General > Compatibility > Graphics Formats
Under the heading 'Export (Save As)' check the box "Save multisheet documents in a single vectorial file"
Then test and verify the result.
Cheers
Mark
I used a different and probably simpler method for myself - I put the commands on a custom toolbar. If you create the toolbar with an empty session, then the toolbar will be present in every workbench.
I've seen things like this periodically; seems to be some kind of minor corruptions in the file. Usually some combination of CATDUA (on the parent assembly or assemblies), or close and reopen, or video driver updates, makes it go back to normal.
Here is one possibility to investigate.
The Physical Product can be linked to multiple different 3DShapes. To say it differently, you can have multiple 3DShapes aggregated to one Physical Product. The Product is what gets represtented on the BOM, the 3DShape is just a representation. So...
I think you'll need to talk to your Administrator / Support People / VAR / whoever does training for this stuff. It's not really something to dive into without some background. But, here's a page from DS online help docs that points to the corner of the system I've referred to, in the web apps...
If you can open the product in ENOVIA / Collaboration and Approvals (the old-style web app), you can click on the history link and get all kinds of records. Up in the header on the page, there's a link next to the word 'Modified.' Clicking on this will give the records of changes to the Product...
