Thanks Hugh and Jeff,
Having never migrated a project (mine never last long enough to span a
release) I would never have thought of using the migration utility to look
for errors. Unfortunately, it didn't find any of importance.
When I opened my assembly the last time and changed an angle constraint
(known mode to cause the error message) I did get a red cross, followed the
bouncing ball and the assembly now seems to be fixed.
Thanks for your time and bother, and for those anxiously awaiting word, the
design review went well this morning.
Ray
"Hugh Henderson (Autodesk)" wrote in
message news:409278d4$1_2@newsprd01...
> Ray,
>
> I think Jeff was referring to the migration utility. It migrates files
> and logs if threre were any problems. Go to Start, Programs, Inventor 8,
> Tools, Migration Utility. There is a setting for a total rebuild. The
> report may list which part has the failing cross-part association in the
> migration utility log file.
>
> Keep us posted.
>
> Best regards,
>
> Hugh Henderson (Autodesk)
>
>
> "Ray Dyson" wrote in message
news:409234df_1@newsprd01...
> > Jeff,
> > Should have been more explicit (as usual for me).
> > I get it when adding every new constraint or editing a part (update) in
an
> > assembly with sub-assemblies. Either upper level parts or parts in subs.
> As
> > I said no red cross or other info available.
> > No I haven't found the offending part yet, it's waiting for just the
right
> > time. I'm off to a design review this morning, guess when it going to
pop
> > up.
> > No sure I understand about migrating and logging but it sounds like a
> > possibility. Please explain migrating, from what to what?
> > VBA? I'm totally programming illiterate!
> > Ray
> >
> > "Jeff Howard" wrote in message
> > news:40919bc6_1@newsprd01...
> > > Memory is definitely failing.... Are you getting an error message in
> > > assembly, but are not sure which part is generating it? Would
migrating
> > > with rebuild all log the part with the problem? Or, do you have the
> part
> > > with the failed association identified and can't figure out what was
> > > referenced? It shouldn't be hard to add the code to query the
database
> > for
> > > "info - parent / child". Possible with VBA? Kick and scream for v9?
> > >
> > > (Wicked Witch of the West; "I'm melting!")
> > >
> > > =================================
> > >
> > > "Ray Dyson" wrote in message
> > > news:40917c86$1_1@newsprd01...
> > > > Hugh,
> > > > Unfortunately the failure I'm getting right now has no red cross.
The
> > > > assembly has about 150 parts, some rather complex with maybe 100 to
> 200
> > > > features.
> > > > I was hoping there might be a shortcut method that I wasn't aware
of,
> > > guess
> > > > not. I'm sure that the culprit will turn up eventually. Right now
it's
> > > just
> > > > a nuisance, not a real problem.
> > > > Ray
> > >
> > >
> >
> >
>
>