Howdy, Stranger!
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
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
"Protect" form/report/dataport
vytjak
Member Posts: 36
Haven't seen this posted anywhere, so...
I've seen a few posts wondering if there is a way to "protect" the code from others. Well, what I'll post here is not a solution, but might be at least a bit usefull sometimes.
Oh, and also, this trick isn't much of a trick, it's simply Navision bug abuse
, which will probably go away in the future.
What you have to do is: on a form (report/dataport) you want to "protect", create a textbox control and as it's source enter static text string, i.e. '123456.....' with a length of about 400 chars (haven't tested for minimum required length). Make it invisible, so it's not cluttering your form. Save it - you're done. Now, if you will try to design the form or export it as a text, Navision will simply crash. You can still run the object without any problems.
Tested on versions 2.x - 4.0.
Cons: you can still access the code using debugger though...
Warning: if you try this on the objects you're using somewhere, backup them first! You've been warned!
I've seen a few posts wondering if there is a way to "protect" the code from others. Well, what I'll post here is not a solution, but might be at least a bit usefull sometimes.
Oh, and also, this trick isn't much of a trick, it's simply Navision bug abuse
, which will probably go away in the future.What you have to do is: on a form (report/dataport) you want to "protect", create a textbox control and as it's source enter static text string, i.e. '123456.....' with a length of about 400 chars (haven't tested for minimum required length). Make it invisible, so it's not cluttering your form. Save it - you're done. Now, if you will try to design the form or export it as a text, Navision will simply crash. You can still run the object without any problems.
Tested on versions 2.x - 4.0.
Cons: you can still access the code using debugger though...
Warning: if you try this on the objects you're using somewhere, backup them first! You've been warned!
Vytenis Jakas
B3 Technologies - Making Technology Serve the People
B3 Technologies - Making Technology Serve the People
0
Comments
wen i try to save the form it says that decimal should be in the range of
-999,999,999,999,999.99 to 999,999,999,999,999.99