Form Functions - CurrForm.<ControlName>.<Function&g

nalinee
Member Posts: 55
Hi everybody,
I am using the following syntax : CurrForm."No.".VISIBLE := FALSE;
But instead of using ControlName("No."), I want to use a variable to which "No." will be initialized.
eg. CustNo := "No.";
Can anyone tell me how the field "No." be made invisible by using variable CustNo?
Thx & Rgds
Nalinee
I am using the following syntax : CurrForm."No.".VISIBLE := FALSE;
But instead of using ControlName("No."), I want to use a variable to which "No." will be initialized.
eg. CustNo := "No.";
Can anyone tell me how the field "No." be made invisible by using variable CustNo?
Thx & Rgds
Nalinee
0
Comments
-
nalinee wrote:Hi everybody,
I am using the following syntax : CurrForm."No.".VISIBLE := FALSE;
But instead of using ControlName("No."), I want to use a variable to which "No." will be initialized.
eg. CustNo := "No.";
Can anyone tell me how the field "No." be made invisible by using variable CustNo?
Thx & Rgds
NalineeTorsten
MCP+I, MCSE NT, Navision MCT (2004,2005)0 -
Can someone help Urgently whether this is possible and easy to implement?
We need to enable the users to define the fields they want to hide and the form to automatically hide those fields.0 -
nalinee wrote:Can someone help Urgently whether this is possible and easy to implement?
We need to enable the users to define the fields they want to hide and the form to automatically hide those fields.
You can find an example for this in older navision version, e.g. 3.70B Form 330, when navision was using this for showing/hiding menues. This logic could be slightly modified.SetSubMenu(MenuType : Integer;Visible : Boolean) CASE MenuType OF 0: CurrForm.Logo.VISIBLE := Visible; 1: CurrForm.GeneralMenu.VISIBLE := Visible; 2: CurrForm.SalesMenu.VISIBLE := Visible; 3: CurrForm.PurchMenu.VISIBLE := Visible; 4: CurrForm.InventoryMenu.VISIBLE := Visible; 5: CurrForm.ResourceMenu.VISIBLE := Visible; 6: CurrForm.JobMenu.VISIBLE := Visible; 7: CurrForm.HumanMenu.VISIBLE := Visible; 8: CurrForm.RMMenu.VISIBLE := Visible; 9: CurrForm.FAMenu.VISIBLE := Visible; 10: CurrForm.MfgMenu.VISIBLE := Visible; 11: CurrForm.CapReqPlanMenu.VISIBLE := Visible; 12: CurrForm.Servicemanagement.VISIBLE := Visible; 13: CurrForm.WarehouseMenu.VISIBLE := Visible; 14: CurrForm.CommercePortalMenu.VISIBLE := Visible; END;
So with this background, you could create a setup table where the users could show/hide the fields in specific forms, read the values for the user who opend the form, and then decided which fields to hide.
Nevertheless, I d not like this idea for normal forms as this will increase support efforts in case users are complaining about things not working and you have to reproduce exactly what they see as the navigation (order) changes moving from one control to the next etc.Torsten
MCP+I, MCSE NT, Navision MCT (2004,2005)0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions