Quote:
Originally Posted by mrstero
I know the 337 error very well. It is Awful!
presumably, you have lots of latent corruptions in your Work manager or Model Manager database ... very interested in your thoughts and experiences with 337 error
|
Actually, we do not use Work Manager or Model Manager; Only windows folders.
With the legacy files of ME10 and CoCreate Annotation, the 337 is populated across plenty of our projects. About 20-30% of our time is rebuilding assemblies because of the 337 error.
If we upgrade to 17 or 18, the LISP/command line code to bypass the 337 error and to fix the file no longer is available to use. Thus, the corruption stays.
The work around is to continuely contact customer support for an override license to fix the problems. BUT, the override is time limited.
So, forever we will be on CoCreate 15.50G unless the option for having the LISP/command line code is returned as a user input. Or, migrate to SolidWorks all of our CoCreate database since we are repairing often enough.
BTW, the code toggling is ...
To fix files ...
(CLUSTER-MANAGER-CONTROL :ALLOW-MISSING-FILES T)
To opt out of the fix ability ...
(CLUSTER-MANAGER-CONTROL :ALLOW-MISSING-FILES NIL)
.