We initially went with the separate CR runtime update here, which did resolve the issue with objects dropping out of reports.  Unfortunately, we experienced an issue after that update where any of the customs reports we'd built for Excel would cause a fatal error when exported in .xls format.  Since we couldn't couldn't quickly diagnose the issue, and since we have many users that rely on those custom Excel reports, we ended up just doing the full service pack upgrade (which resolved both issues).

Regardless, good luck!  David is right - it's a nasty bug.

Ian

On Tue, Feb 17, 2015 at 8:26 AM, Parsell, David <[log in to unmask]> wrote:

True, the latest TMS service pak will solve that problem, but only because it contains the latest CR file that corrected the problem.

 

Dimitry can point you to the right file without having to do a full service pak upgrade.

 

I bet if you looked at all of the TMS reports, you would find them all dropping the last record on each page.

 

It’s a very nasty bug, because it is difficult to find without very tedious checking.

 

Good luck with it.

 

David Parsell

 

From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Eckert, Ian
Sent: Tuesday, February 17, 2015 8:00 AM
To: [log in to unmask]
Subject: Re: FW: TMS report problems

 

Hi LaNore,

We experienced the same issue here, and I believe the culprit was a bug in an older version of the Crystal Reports runtime.  What build of TMS are you currently using?  For us, upgrading to the newest service pack for TMS2012 (SP2) resolved the issue.

Ian

 

On Mon, Feb 16, 2015 at 1:57 PM, LaNore, Ruth, DCA <[log in to unmask]> wrote:

Hi All,

 

I’m forwarding the request below on behalf of my colleagues. It turns out she is not the only curator here with this problem. Has anyone worked out a solution?

 

 

I have been having a problem with Crystal Reports and working with IT on it. Is anyone else having an issue when printing a report (Object List with Image) of a package and the last image on each page does not print? It is not simply a function of scaling the page for printing because the numbering going from the bottom of one page to the top of the next page is correct. But the reporting function drops one object per page from the report. I discovered it by comparing, for the same object package, the print-out of one object per page and the Object List with Image report. I am trying to determine if it is something specific to my computer or if it is a TMS glitch.

 

 

Ruth LaNore

Registrar

Museum of International Folk Art

P.O. Box 2087

Santa Fe, NM 87504

505.476.1218

www.moifa.org

Subscribe to MOIFA  E-News

 

To unsubscribe, send an email to [log in to unmask] with the following commands in the body of the email:

signoff TMSUSERS

// eoj

You will receive a confirmation that your subscription has been removed.




--

Ian Eckert
Manager, Collection & Exhibition Technologies (CE-Tech)
The Museum of Modern Art

11 West 53rd Street  New York, NY 10019

To unsubscribe, send an email to [log in to unmask] with the following commands in the body of the email:

signoff TMSUSERS

// eoj

You will receive a confirmation that your subscription has been removed.

To unsubscribe, send an email to [log in to unmask] with the following commands in the body of the email:

signoff TMSUSERS

// eoj

You will receive a confirmation that your subscription has been removed.




--
Ian Eckert
Manager, Collection & Exhibition Technologies (CE-Tech)
The Museum of Modern Art

11 West 53rd Street  New York, NY 10019
To unsubscribe, send an email to [log in to unmask] with the following commands in the body of the email:

signoff TMSUSERS

// eoj

You will receive a confirmation that your subscription has been removed.