The all knowing and genius extraordinaire Geri Moxley looked at my
report and in two seconds diagnosed the problem.  I had linked ObjectID
in the Objects table to OBJRightsID in the Rights table instead of to
ObectID.  Once that was fixed, all was solved.

 

Just think of the damage I could do to things if I didn't have you guys
to bounce my embarrassing moments off of like this?

 

Thanks a million!

 

David

 

David Aylsworth 
Museum of Fine Arts, Houston 
Registrar for Collections 
telephone:  713-639-7824 
fax:  713-639-7780 

________________________________

From: The Museum System (TMS) Users [mailto:[log in to unmask]]
On Behalf Of David Armstrong
Sent: Friday, July 18, 2008 4:26 PM
To: [log in to unmask]
Subject: Re: phantom data in crystal reports

 

You only have two tables, Objects and ObjRights?  Are you sure that the
Restriction data really isn't in the ObjRights table?  Have you done
some SELECT statements against ObjRights to verify that the data really
isn't there?  For example you could do something along the lines of,

 

SELECT * 

FROM ObjRights

WHERE restrictions like '%<insert bogus data here>%'

 

________________________________

From: The Museum System (TMS) Users [mailto:[log in to unmask]]
On Behalf Of Aylsworth, David
Sent: Friday, July 18, 2008 2:15 PM
To: [log in to unmask]
Subject: phantom data in crystal reports

 

Happy Friday, everyone...

Have any of you had an issue of "phantom" data showing up in a crystal
report on your records when the data is not anywhere in the field for
the record itself?  I've got a crystal report that pulls up, among other
things, copyright restrictions.  The OBJRights table is linked to
Objects with a left outer join, and the "Restrictions" field is included
with nothing fancy.  

I've got a batch of records for objects accessioned between 1968-1972
that when I run this report on them, extensive copyright restrictions
that came with a collection in 1991 show up on the report.  There is
nothing in the restrictions field in TMS for them.  And, when I put in
jibberish for a restriction, the jibberish will not show up, but the
bogus restrictions still do.

Since recently accessioned objects that had new records created
individually for them function properly, I thought maybe this was
something affecting any records that were converted from our previous
db, but I've pulled up plenty of records that came over in the
conversion that function right.  As far as I can sleuth out, it is
restricted to accessioned objects accessioned between 1968-1972.  That
was prime time for hallucinogenics, but this is too much of a trip for
me on a Friday afternoon.  

Any ideas?

I appreciate any help you can give...

Thanks,

David

David Aylsworth

Museum of Fine Arts, Houston

Registrar for Collections

telephone:  713-639-7824

fax:  713-639-7780