Yet another discovery: undocumented message file oem.iem

[Oh No! Here he goes again!] Last friday, right before leaving for a nice weekend at Isola delle correnti (the south most edge of Sicily, southern than Tunis), I did another of my strange experiments: added to 4glusr.msg a custom error message and wrote a little 4gl program calling err_get to see if 4gl was able to access the newly added message. Why would anybody in is right mind do something like that? Off the top of my head, two good reasons - multilinguistic support (even though my CASE has this built in) and hardwiring to 4gl messages common to all applications used in one site. It was sheer luck that the message number chosen was 30000 and not (say) -997, because, rather than getting the expected "Marco's silly message" or "Unknown error message: 30000" the program joyfully replied "Cannot access message file oem.iem". Oh, well, if Informix, unsolicited, decided to provide an oem message file, then the idea must have looked good even to them! Quickly wrote and compiled the requested message file, and pronto, I was able to access my custom message. Needless to say, I could find no reference whatsoever to this hidden message file in the manuals or release notes. Admittedly, we're not oem's. Nonetheless, we would like to use this feature, so, is there anybody out there that knows: 1) If this feature will be supported in the future 2) what is the useful range of messages that can be safely used (I bet that Informix employees among us are able to answer my questions) TIA, marco ____________________________________________________________________________ rem radioterapia, which I immeritately manage, seldom agrees with what I say marco greco (Catania, Italy) Work: marcog@ctonline.it rem radioterapia 39 95 447828 fax 446558 (was mar.greco@agora.stm.it) Achea 39 95 503117