Mike, Kevin, I would be most pleased if you could advise on this, or perhaps suggest a mechanism which could make this work.

Here in Europe, for monetary and quantity values, the comma is not always used as the thousands separator. As such, we can code our programs to use MD2, or MC2, conversions.

Dictionaries on the other hand are more difficult, and indeed are client specific, as we may sell our product to users in the UK (commas) or part of Europe (period).

My plan was to write a program to convert MD to MC in the conversion field in all table dictionaries, so that the user could convert these as a part of their installation.

Problem is that the Works subscription, section 'Database Administration' has a sentence which reads 'Indexes and Dictionaries may not be modified'.

I beleive that this clause is restrictive, and would request clarification on this statement.

I am not prepared to have multiplie definitions.

Luckily I completely removed any database associated controls from any forms, as all forms in my application are now totally hard coded, so that views and the like can use MD or MC conversions as per my code.

Clarification on licence, and suggestions as to how best to approach this please.

Furthermore, it would be brilliant (maybe you have already done it and I am not aware), if in OI 7 you could add an environment variable to have a switch. I would not like see any change to MD or MC conversion, but perhaps a new one called MV (Masked Value) which uses the environment variable and does MD or MC as appropriate.

This environment variable could perhaps default to the users workstation setup, but my preference would be to be under program control.

Your thoughts please.

Thanks, Colin

=== At 05 JAN 2005 04:07AM support@sprezzatura.com wrote: ===

MX always used to do this although we have not tried it recently. (It would default to the language set conversion specified cf DX etc.

Failing that you could ship two RDK installs with the product that contained both versions of the dictionary items. You could run these based on a user specified trigger. While an RDK is running it legitimately becomes a licensed development version.

support@sprezzatura.com

The Sprezzatura Group Web Site

World Leaders in all things RevSoft

MX is decimal to hex conversion.

I dont want to have two sets of dictionaries to maintain, so separate installs is not viable. In addition, one installation may do work for clients in different countries.

Using the locale would be a start, but really need to have control by the system.

I suppose I can use the OCONV overrides in RLIST, as a slightly messy alternative.

Colin

We've just checked the AREV docs which this all used to work in. It was DX, MOX etc. At first glance this doens't seem to be working in OI but all the ENV_APPNAME and LND_LANGUAGENAME rows still exist in SYSENV so we don't know whether they are meant to work.

support@sprezzatura.com

The Sprezzatura Group Web Site

World Leaders in all things RevSoft

Here's another idea. Create your own language independent Iconv/Oconv routine. It could check the language of choice and appply the correct conversion.

HTH,

john

K.I.S.S.

Gotta love it…

support@sprezzatura.com

The Sprezzatura Group Web Site

World Leaders in all things RevSoft

Perhaps I rewrite OI to make it work in the real world.

If you've got a price, make me an offer

Mike

Oh, I am quite cheap, a few pizzas will do :)

Colin et al-

DX conversions (all of the 'XCONV' conversions 'DTX,MSX,BX,MOX,DX,MTX' ) appear to be programmed in.

Both Iconv(RTP26) and OCONV/FMT(RTP19) support them.

It seems as though they have never worked in OI. We're working on that now, and will let you know a project release date.

Mike

All-

Fixed. This will be in the next update of 7.1, due out when we finish our testing.

Thanks-

Mike

My god that was fast.

Well done, I look forward to trying it out.

Colin

View this thread on the Works forum...