Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Using out-of-licence tables
Urmas
Member Posts: 76
My associate here just discovered, that there is possible (at least up to version 3.7) to use tables, not allowed to be used by your license as temporary tables.
It means that you can create a table (using your developer license) in the number range not accessible by your customer. You can use the table in your forms / reports / codeunits / etc as long as you do not actually write into database in this table - eg use it as temporary (memory) table.
This approach can save some amount of money for your customers as they do not have to buy licensed number areas for buffer tables. Also it allowes developers more flexibility as you can use separate buffer tables for different tasks instead of using one universal one for all tasks.
It means that you can create a table (using your developer license) in the number range not accessible by your customer. You can use the table in your forms / reports / codeunits / etc as long as you do not actually write into database in this table - eg use it as temporary (memory) table.
This approach can save some amount of money for your customers as they do not have to buy licensed number areas for buffer tables. Also it allowes developers more flexibility as you can use separate buffer tables for different tasks instead of using one universal one for all tasks.
0
Comments
I believe it has something to do with the fact that temporary tables are held in the clients memory and not in the database server (where I presume license validation is done)