Search results for query: *

The crashes happen on brand spanking new models as well as old legacey assemblies and we are running build code M110.

You have to have 4GB to command windows to use the 3GB switch.

We are.

We have over 80 users at any given time located in various parts of the country. We all have the same machine except for one individual who is testion out a 64 bit machine with 8GB of RAM. The group I'm in work with so large of assemblies on a daily basis, we are forced to work in simplified...

Due to unexpected exits, corrupt workspaces and script erroes, I have logged 161 minutes of lost work I had to redo since the 14th of November. (Today is November 15)

I wish the answer was that simple, all 12 individuals were wrking from an active WS. I wish it was as simple as operator error but it isn't. I have read on other boards of similar activity, so it looks like it's not just us.

Is anyone experiencing assembly files reverting back to a prior iteration? We are running PDMLink 8.0 with WF3 M110. So far 12 individual users have experienced and continue to experience assemblies that revert back to a prior iteration. The assembly gets checked into commonspace with hard...

It's not just WF3, we have been crashing ever since we started with WF2. We're getting ready to upgrade to build code m120 as soon as it's released. The only thing I can say is it has gotten extremely worse since we upgraded to WF3. We have noticed over the past month that the incidents have...

It has gotten so bad for us, we have also started keeping excel sheets to log our lost time. I know off hand of 12 different people who have been using Pro/E for years that have "checked in" (PDM Link lingo) assemblies and have hard copies of their final work to only open the assembly at a...