Customization and Integration

[hmurat]

Good Morning,

I'm trying to use a .NET TextLookup control in a Customizer launched DLL.  Because the TextLookup requires a Session as a parameter and I don't have one, I must create one. 

"Service.GetSessionContextXMLFromCommand(CommandLine)" is blank so I create a Session object basically from scratch, and it forces the user to log in again when this form is launched.

Does anyone know a way around this?  We haven't done any VB6 development thus far and we'd like to keep it that way for consistency.

Thanks very much,

Hugh

[LouDavis]

I don't believe you will be able to do what you would like to through Customizer, as I don't believe you have access to moclass.moSysSession which contains the Session information for the task you launched Customizer through.  Even if you were capable of getting to this, I don't think it would work with a .NET application very well  even if you passed the object to your DLL. 

"Service.GetSessionContextXMLFromCommand(CommandLine)"  is blank because you didn't launch your task as an EXE from the Business Desktop, which passes the information as a command line parameter to your exe.  The MAS 500 .NET framework doesn't include functionality to determine if an existing MAS 500 session is currently running on the same machine as it can do with the VB 6 ActiveX EXEs. 

I would recommend a redesign of your DLL to drop the .NET TextLookup control and have some generic type of functionality to look up the data you need that isn't dependent on the MAS 500 Session.   Also, if you haven't done so already, ensure your .NET control is COM compliant and compiled for x86 processors ONLY so your vbScript can call it.  Then I would recommend going out to Sage's MAS 500 enhancement site to request the additional functionality you would like to see added to Customizer that you would need to accomplish your original goal..  I understand that Sage is making improvements to Customizer, so maybe you can get you request slipped in.

[hmurat · Accepted solution]

Thanks for the reply and insight.

I have gone ahead to the Sage MAS 500 Ideas page (https://www11.v1ideas.com/SageERP/MAS500/Idea/Detail/2492) and submitted this idea there.  If anyone else would find this change beneficial, please vote for it.

In the past we've used simplified forms (text fields and select boxes) to get around this limitation.  Until this is addressed, we'll continue to do so.