--- In guide-user@yahoogroups.com, Bill J Gray <pluto@...> wrote:

>
> Hi Denis,
>
> It's still a puzzler, I'm afraid...
>
> "... An old file did not cause problems but it also does not
> have a space added prior to the name. This would indicate that
> Guide uses the info when no asteroid are loaded as part of the
> install. Am I right?"
>
> Yes, but the name data from 'mpcorb' are _always_ used
> when 'Use MPCORB' is checked in the Extras menu. That is
> to say, either all data (orbital elements plus names,
> numbers, and provisional designations) comes from Guide's
> built-in data, or they come from MPCORB. They cannot be
> mixed-and-matched, because the order of the objects will
> be quite different.
>
> I've tried to duplicate what you describe, still without
> success. It may help to know this: when you tell Guide to
> label objects by name and provisional designation, are _any_
> asteroids labelled, or are they all "anonymous"? And can
> you tell Guide to "go to" Vesta, or Eris, or 2007 GA, or
> asteroid 150000?
>
> I mention these because with its built-in data, Guide should
> be able to find Vesta. But the others are more recent objects.
> And if Guide can find them with the Go To... Asteroid function,
> it ought to be labelling them, too.
>
> -- Bill
>

Hi Bill,
if I use the MPCOrbCR.dat I do not have any label shown
setting "label and provisional name" while I have all the label
shown using the MPCOrb.dat.