Setting the "server name' in VLF

This Q&A forum allows users to post and respond to "How Do I Do ....." questions. Please do not use to report (suspected) errors - you must use your regional help desk for this. The information contained in this forum has not been validated by LANSA and, as such, LANSA cannot guarantee the accuracy of the information.
Post Reply
dhnaigles
Posts: 56
Joined: Wed Feb 03, 2016 1:34 am
Location: Marlborough, MA, USA

Setting the "server name' in VLF

Post by dhnaigles »

If I am doing a private connect and I am choosing from the servers defined in VLF, how can I replace the "Server Name" text at the bottom of the VLF with the server info I am connecting to? It always says "Local".
MarkD
Posts: 692
Joined: Wed Dec 02, 2015 9:56 am

Re: Setting the "server name' in VLF

Post by MarkD »

Try #FIM.uStatusManager.uConnectId := "xxxxxxxxxxxx"
dhnaigles
Posts: 56
Joined: Wed Feb 03, 2016 1:34 am
Location: Marlborough, MA, USA

Re: Setting the "server name' in VLF

Post by dhnaigles »

Mark
#FIM is not available in the avPrivateConnect routine. Any alternatives?
MarkD
Posts: 692
Joined: Wed Dec 02, 2015 9:56 am

Re: Setting the "server name' in VLF

Post by MarkD »

Try this global declaration in your reusable part:

Define_Com Class(#vf_sy150) Name(#FIM_MainWindow) Scope(*Application) Reference(*dynamic)

then use #FIM_MainWindow instead of #FIM.

PS: There might be a timing issue with the status bar getting set up, in which case try moving the #FIM_MainWindow declaration into your system IIP and set the connection name in your avMainWindowReady method.
Post Reply