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 CodeCoverage from Command Line
greatscott001
Member Posts: 32
Not a question really but just a hint for anyone else who runs into this. I have been struggling to run Code Coverage from the command line at a client's site using the command:
I could not get it to work while it worked fine locally it would not work at the client.
The resolution was to make sure the there is a FIN.FLF in the same folder as the FINSQL (or FIN.EXE). Even though the SQL server had a valid license, it would appear it needed a local license to enable the use of the Coveragelog parameters.
Hope this saves someone else some time and frustration.
FINSQL Coveragelog, Coveragefilename=c:\temp\coverage.log
I could not get it to work while it worked fine locally it would not work at the client.
The resolution was to make sure the there is a FIN.FLF in the same folder as the FINSQL (or FIN.EXE). Even though the SQL server had a valid license, it would appear it needed a local license to enable the use of the Coveragelog parameters.
Hope this saves someone else some time and frustration.
0
Answers