Sorry Dave. Reading on an iPhone and didn't understand the Reply came after a clip of the original email.
Dave On Apr 24, 2012, at 5:37 PM, "Shellman, David" <[email protected]> wrote: > So why is the app server uni-code compliant? > > On Apr 24, 2012, at 5:35 PM, "Easter, David" <[email protected]> wrote: > >>> BMC (Remedy) has always stated that its a bad idea to mix languages in your >>> database. >> >> That was true prior to 7.0.00 - but hasn't been true now for almost 7 years >> now. Using Unicode as your character set enables you to have multiple >> languages (but not multiple character encodings) in your database. >> >> Were you to be able to start over, the recommendation would be to use >> Unicode. >> >> Also note that the Remedy user client is not Unicode safe, so if using >> Unicode - use the web client. >> >> -David J. Easter >> Manager of Product Management, Remedy Platform >> BMC Software, Inc. >> >> The opinions, statements, and/or suggested courses of action expressed in >> this E-mail do not necessarily reflect those of BMC Software, Inc. My >> voluntary participation in this forum is not intended to convey a role as a >> spokesperson, liaison or public relations representative for BMC Software, >> Inc. >> -----Original Message----- >> From: Action Request System discussion list(ARSList) >> [mailto:[email protected]] On Behalf Of Sean O'Sullivan >> Sent: Tuesday, April 24, 2012 1:59 PM >> To: [email protected] >> Subject: Mixing Languages in the Database >> >> Good Afternoon Listers, >> >> BMC (Remedy) has always stated that its a bad idea to mix languages in your >> database. They state that you risk currupting the database. >> >> Because of this we put up a Japanese Remedy server for Japan when we started >> supporting businesses there and its working fine. >> >> However, we have a problem in that sometimes users enter other languages >> into our worklogs of our English language Remedy system. (Polish, Japanese) >> The text doesn't show up properly in the Remedy client. It looks like >> garbage. >> We told users not to enter non-english text, but sometimes they do anyway. >> >> >> This has not caused us a problem so far, but I am concerned about it >> eventually currupting our database as BMC warned. >> >> My two questions are: >> >> 1. Has anyone had any database curruption issues caused by someone entering >> non-English characters in an English language Remedy? >> >> 2. Does anyone know of a way to put in code to prevent other languages from >> being entered? >> >> >> I thought about something at the database level....maybe a trigger... >> >> Thanks for any input you may have. >> >> Sean O'Sullivan >> Prudential Financial >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
