TMSUSERS Archives

The Museum System (TMS) Users

TMSUSERS@SI-LISTSERV.SI.EDU

Options: Use Monospaced Font
Show HTML Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jon Thristan <[log in to unmask]>
Reply To:
The Museum System (TMS) Users
Date:
Fri, 1 Dec 2017 18:09:28 +0000
Content-Type:
multipart/related
Parts/Attachments:
text/plain (6 kB) , text/html (23 kB) , image001.png (45 kB) , image002.jpg (45 kB) , image005.gif (5 kB) , image006.jpg (5 kB) , image007.jpg (5 kB)
Hi All

Just a quick update on the below, as Gallery Systems appreciate that any report of potential data loss is concerning.

I connected with the user who reported the issue at The National Gallery, London, and we carefully created further Object records, starting from within the Exhibitions module. We weren't able to replicate the problem. We're investigating the version of the ODBC driver being used: we weren't able to check the System DSNs, but we could see that Personal ones used SQL Native Client 10.0, rather than SQL Native Client 11.0, which should be used with TMS 2016 R2. Gallery Systems have had reports, in the past, of peculiar TMS behaviour where an incorrect ODBC driver has been used.

We're keeping a watching brief on the issue and if we find out anything further I'll provide an update.

Best wishes
Jon

Jon Thristan MBCS | Project Consultant
[log in to unmask]<mailto:[log in to unmask]> | +44 20 7993 8402
GallerySystems | www.gallerysystems.com<http://www.gallerysystems.com/>

----

[cilogo_60]

Join us in L.A. this December for
Collective Imagination 2017

The International TMS Users Conference
Workshops:  December 4 - 5, 2017
Conference: December 6 - 8, 2017

Get more details here<http://www.gallerysystems.com/ci-2017/>.



From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Shepherd, Rupert
Sent: 30 November 2017 15:31
To: [log in to unmask]
Subject: Re: Object records not being saved in Exhibitions module

Dear colleagues

Many thanks for this help; but alas, our problem is not that exhibition object records do not refresh when edited in the Objects module, or vice versa. We are encountering exhibitions object data - such as Statuses - that are not saved when the focus shifts to another module or, indeed, when File --> Save is clicked. In other words: TMS is failing to save when it should, in this context.

Best wishes

Rupert

Rupert Shepherd, PhD FSA
Collection Information Manager
[log in to unmask]<mailto:[log in to unmask]>
Tel: +44 (0)20 7747 5921

From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Rob Morgan
Sent: 30 November 2017 15:25
To: [log in to unmask]
Subject: Re: Object records not being saved in Exhibitions module

Hi everyone,

You can't do the following function in 2012, but in 2017 (the version we're using in Baltimore) if you click Exhibition Objects, there is a Refresh Exhibition Object from Object Records option.

I think this feature is in 2016R2.  Rupert, does this solve your problem?


-          Rob Morgan (Baltimore Museum of Art)

[cid:image001.png@01D36ACE.2BF99320]

From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Catherine Nguyen
Sent: Thursday, November 30, 2017 10:03 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: Object records not being saved in Exhibitions module

Hi Rupert,

I just learned that the Exhibitions module and the Objects module do not link with their changes, at least on ours (We're still on TMS 2012). From what I've been told, TMS keeps these two separate because when some objects travel, they can go under different numbers, have different names, etc... However, this can be changed on the back end for the two modules to link.  How this is done, I have no idea.  Always enter the object for the first time in the object module, create the exhibition, then add the objects into the exhibition that way. It's unfortunate that the default isn't that these two link.

I'm curious to hear what others may have to contribute to this post... there may be a solution I'm unaware!



[cid:image002.jpg@01D36ACE.2BF99320]  Catherine Nguyen
  registrar
   [log in to unmask]<mailto:[log in to unmask]>

40 East Erie Street | Chicago, IL 60611
DriehausMuseum.org<http://driehausmuseum.org/> | Direct: 312-874-5907
Main: 312-482-8933 | Cell: 312-636-2865


From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Shepherd, Rupert
Sent: Thursday, November 30, 2017 7:08 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Object records not being saved in Exhibitions module

Dear colleagues

I have a user who reports that she is editing exhibition object records in the Exhibitions module, choosing File --> Save, and finding that her changes are not saved - never mind changes being lost when she navigates away without choosing Save. Has anyone else encountered this, and can you offer a solution? We're using TMS 2016 R2.

With thanks and best wishes

Rupert

Rupert Shepherd, PhD FSA
Collection Information Manager
[log in to unmask]<mailto:[log in to unmask]>
Tel: +44 (0)20 7747 5921

[Image removed by sender. The National Gallery, Trafalgar Square, London WC2N 5DN]<http://www.nationalgallery.org.uk>
[Image removed by sender. Monochrome: Painting in Black and White]<https://www.nationalgallery.org.uk/whats-on/exhibitions/monochrome-painting-in-black-and-white>
To unsubscribe, send an email to [log in to unmask]<mailto:[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]<mailto:[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]<mailto:[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]<mailto:[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.


ATOM RSS1 RSS2