As the people at E-frontier found out they shouldn't be using relative paths anyways since there are no ambiguitys in a full path name.  It can really botch things up if a file gets exported with path name.  You should have seen the mess it casused when Poser went to full path names from relative ones. 
I tried telling it that that library was a Poser library but it didn't seem to take.  I ended up with a mess of entrys none of which are useful instead of what I told it.  I think I'll load the new update and try once again.  Could be that it's something as simple as a missed mouse click.