Thanks! I've just raised a ticket with GS, so no doubt they'll say the same thing - but I'll pass your note straight to our IS team to make sure they carry out the client upgrades correctly.

Many thanks for this!

Rupert

From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Brad Hubley
Sent: 01 December 2016 17:20
To: [log in to unmask]
Subject: Re: TMS 2016 bug in spell checker?

Hi Rupert,

As mentioned below 2016 R2.  We've learned from GS that a proper installation requires an uninstall of any previous version of TMS then a reboot of your PC and then installation of 2016 R2.

Brad

From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Shepherd, Rupert
Sent: December-01-16 12:14 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: TMS 2016 bug in spell checker?

Brad, thanks. Which version are you on?

I've just tried this again on our 2016 R2 implementation, and it's definitely still happening for us - after a reboot and everything.

<sigh/>

Best wishes

Rupert

From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Brad Hubley
Sent: 30 November 2016 18:56
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: TMS 2016 bug in spell checker?

I just tried this in the Object History field with the following:

"This is a test
of the spell-cheqquer"

Then I followed your steps, editing "cheqquer" to "checker" in the upper pane, clicking on Change and "cheqquer" was changed to "checker".

Brad

From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Shepherd, Rupert
Sent: November-30-16 10:26 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: TMS 2016 bug in spell checker?

Dear colleagues

Has anyone noticed a bug in the spell checker, as follows:

1.       In a Text Entries field, enter text which contains line or page breaks

2.       Open the spell checker and, rather than choose an offered alternative word, edit the text in the upper pane and press the Change button

3.       The characters you thought you edited have not been changed, but others have / insertions end up in the wrong place?

I've come across this in our trial version of TMS 2016 R2, and am curious as to whether it's a known issue in this or previous releases, or not.

Thanks!

Rupert

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

[The National   Gallery, Trafalgar Square, London WC2N 5DN]<http://www.nationalgallery.org.uk/>
[Help us support our future -   As a charity the National Gallery needs your support to ensure we continue to be one of the world's great art galleries]<https://www.nationalgallery.org.uk/support-us>
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.

[Chihuly. Now Open. À l'affiche.]<https://www.rom.on.ca/chihuly>
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.

[Chihuly. Now Open. À l'affiche.]<https://www.rom.on.ca/chihuly>
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.