Forum

Hello,

We are having trouble puting our &AtClient code inside our managed forms to a common module. It seems that in a managed form if you have a procedure &Atclient the only procedures that are visible are local procedures of that form (&AtClient or &AtServer).If i create a global common module (and tick the client on the properties)  the procedures i define there are not accesible by a managed form. Is this by design or we are missing something? .Because of this we have a lot of code duplication in our forms.

Hello, Constantinos Anastasiou.

The common module can be accessible for client or not depending on the settings of the module. If you want to call a procedure of a server common module from the client (&AtClient), that server method should have Server call option enabled. Otherwise you need to call that procedure from the server (&AtServer) procedure.

Maybe You forgot add key word Export? Like:

Procedure CalculateTotal (TabularSectionRow) Export

As i mentioned on my initial post with &AtServer modules its fine. the problem is with code &AtClient whicj i need to put in a common module.

For example lets say i have this code in a command inside a managed form:

&AtClient 
Procedure ScanOnChange(Item) 
  qForm = GetForm("CommonForm.InputQuantityForm");
  searchQuantity = qForm.DoModal();
EndPRocedure.

So You want connect form's element event with common module code directrly? You can't do this. You need both code in form and in common module:

&AtClient
Procedure ScanOnChange(Item) 
    searchQuantity = YourCommonModule.SearchQuantity();
EndProcedure