My question is simple, is there any workaround possible to allow storage of the euro symbol €, without the need for unicode?
Is there, for example, any way I could use WE8MSWIN1252 - Microsoft Code Page 1252 - which (I quote):- "Microsoft Code Page 1252 - Western European. Very similar to ISO 8859-1, except for the inclusion of additional characters. Includes the euro symbol, trademark (TM) symbol, and oe ligature, but using a different codepoint than ISO 8859-15" - would this work for me without the database needing to be unicode?
If yes, would it mean losing any other non-unicode characters like £ or $?
Note: part of the reason for my post is having migrated data from Essbase 7 (non-unicode) where the client had excel add-in working with member alias values that had € in them working successfully, migrated to 18.104.22.168. the same functionality does not work, without migrating to unicode where excel add-in is no longer an option, and my client is strongly bonded with excel add-in...
thanks for your input,
I can understand your client that he is strongly bonded with the classic Excel AddIn.
Was the Euro symbol in the database as a member ID (alias) instead of EUR? Or was it part of Excel with the cell formatting?
Unicode is unicode. The (Microsoft) code page is a different story.
I would try this in development. As it described, the code page translates an input into an output. It should not change the input.
I mean that when things go wrong, you might have some work to get it undone. Therefore I recommend the tricky things always to be done in development. This is new territory - you can see in the amount of answers.
Maybe write the solution here when you have succeeded.