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
- 384 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
Report Server
Waldo
Member Posts: 3,412
When a database is filled with lots of records (let's say, 70 Gb), it can take a long time for printing a report.
May be a solution to this is building a "Report Server". A stand-alone application that reads a table where records are inserted when a user prints a record. When a record is found, this "Report Server" is printing the report.
So, as big advantage, the user does not have to wait until his fat client has composed the record to print the report, but just has to insert the record with the needed parameters in one table.
The "Report Server" reads the record, and prints the report.
If somebody has remarks about this, please tell me. Bad idea? Experience doing a similar thing? Tips and tricks for developing this? Please let me know!
May be a solution to this is building a "Report Server". A stand-alone application that reads a table where records are inserted when a user prints a record. When a record is found, this "Report Server" is printing the report.
So, as big advantage, the user does not have to wait until his fat client has composed the record to print the report, but just has to insert the record with the needed parameters in one table.
The "Report Server" reads the record, and prints the report.
If somebody has remarks about this, please tell me. Bad idea? Experience doing a similar thing? Tips and tricks for developing this? Please let me know!
0