I’m working on a multilingual application and I need to be able to translate longer messages than the LangTrans table can hold. The MsgSvc table seemed like the perfect place for these longer messages. I thought I’d add an instance of cMsgSvcObj to the goApp object so that it’d be available to me from any of my forms. The problem I’m running into is that v_msgsvc is based on the MsgSvc table. This table is opened and a modified version of it is used by oLanguageMgr. When cMsgSvcObj loads, it doesn’t bother opening MsgSvc again, because it’s already open. The view pulls from this open version of the table, which is NOT the same as the “real” table. Now the v_msgsvc cursor doesn’t contain all of the language records needed, so I’m finding I can’t retrieve localized messages from it (it’s missing the other language records).

I suppose I could explicitly close MsgSvc from the OpenTables() method in the DE of cMsgSvcObj. However, this will probably break the LanguageMgr object. Reestablishing the table (via a call to LanguageMgr from cMsgSvcObj) would majorly couple these two objects together, and I’m sure still wouldn’t work; I don’t think I want to even attempt to go this route.

Is there anyway to get the cMsgSvcObj to open in its own datasession? I know this happens when it’s running as a COM object, but I don’t see any code to “force” this. I seem to remember this coming up before as an ER, or as something that was/is in the framework, but I can’t remember.

Do anyone have any suggestions for this?