AnsweredAssumed Answered

Problems with design tables

Question asked by 1-GTQX2P on Dec 10, 2008
Latest reply on Dec 11, 2008 by 1-GTQX2P

Like • Show 0 Likes0
Comment • 2

We are working with assemblies in wich all the parts included have DT (external ones). The assembly and the subassemblies have also DT.

The problem is that many times opening the assembly, not all the tables are edited and updated, most of the times, the last assembly to be opened (the main assembly) is not updated. I don't know why, because if I close this assembly leaving opened the parts, and I open again the assembly, it's updated. The thing is that is not possible to be sure if is going to be updated or not, because is making the error ramdomly.

Other times we have a message from SW like: " There's no enough memory to complete the operation", "It's not possible to the carry out the server aplication" (sorry, but I'm traslating directly from Spanish, so maybe it is not exact).
Other times, SW is resumed directly.
A complete nightmare!!

Does anyone have this problem, or somethig similar?

We are thinking that maybe is something we are doing wrong, but maybe can be the Office version, 2007?, or something wrong with SW?

Someone can help?
Thanks

No one else has this question

Outcomes

Jeff Mirisola Dec 10, 2008 3:53 PM

Sonia,
When dealing with design tables on multiple layers, it's often necessary to rebuild a couple of times depending on how deep the changes are or need to go.

As for your error message, it sounds like you're maxing out your RAM. What are your system specifications (CPU, RAM, OS, etc).

Actions

1-GTQX2P @ Jeff Mirisola on Dec 11, 2008 5:33 AM

Hi Jeff, thanks for your answer.

About system specifications:
Intel Core 2 Quad CPU
Q6600 @ 2.40 GHz
2.40 GHz, 3,50 GB de RAM
NVIDIA Quadro FX3700

Ah, something else: If I open the assembly without the preview view when opening, each part or assembly is being updated when is opened, but it's at the end, when it is opening the last or two last assemblies when they are not updated.
If I try to open the assembly with preview view, the opening order is the opposite, so the first assembly to being opened and updated is the main, and then deep and deep. But the problem this way is that there is a subssembly that makes the SW to be closed automatically. Maybe is something wrong with this subassembly. I'll try to do it again.

Any idea?

Actions

2 Replies

Jeff Mirisola Dec 10, 2008 3:53 PM
Mark Correct
Correct Answer
Sonia,
When dealing with design tables on multiple layers, it's often necessary to rebuild a couple of times depending on how deep the changes are or need to go.

As for your error message, it sounds like you're maxing out your RAM. What are your system specifications (CPU, RAM, OS, etc).
Like • Show 0 Likes0
Actions
- 1-GTQX2P @ Jeff Mirisola on Dec 11, 2008 5:33 AM
  Mark Correct
  Correct Answer
  Hi Jeff, thanks for your answer.
  
  About system specifications:
  Intel Core 2 Quad CPU
  Q6600 @ 2.40 GHz
  2.40 GHz, 3,50 GB de RAM
  NVIDIA Quadro FX3700
  
  Ah, something else: If I open the assembly without the preview view when opening, each part or assembly is being updated when is opened, but it's at the end, when it is opening the last or two last assemblies when they are not updated.
  If I try to open the assembly with preview view, the opening order is the opposite, so the first assembly to being opened and updated is the main, and then deep and deep. But the problem this way is that there is a subssembly that makes the SW to be closed automatically. Maybe is something wrong with this subassembly. I'll try to do it again.
  
  Any idea?
  Like • Show 0 Likes0
  Actions

Problems with design tables

Outcomes

Related Content

Recommended Content