Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft Dynamics NAV 2009 Programming Cookbook

You're reading from   Microsoft Dynamics NAV 2009 Programming Cookbook Build better business applications with NAV

Arrow left icon
Product type Paperback
Published in Oct 2010
Publisher Packt
ISBN-13 9781849680943
Length 356 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Matthew Traxinger Matthew Traxinger
Author Profile Icon Matthew Traxinger
Matthew Traxinger
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Microsoft Dynamics NAV 2009 Programming Cookbook
Credits
About the author
About the reviewer
1. Preface
1. Strings, Dates, and Other Data Types FREE CHAPTER 2. General Development 3. Working with Tables and Records 4. Designing Forms 5. Report Design 6. Diagnosing Code Problems 7. Roles and Security 8. Leveraging Microsoft Office 9. OS Interaction 10. Integration 11. Working with SQL Server 12. The RoleTailored Client Index

Setting breakpoints


Stepping through code line-by-line or function-by-function can take forever. Luckily there is an easy way to tell the debugger to stop right where we want it to.

How to do it...

  1. Create and save the same codeunit discussed in the Using the debugger recipe in this chapter.

  2. Design the codeunit.

  3. Go to the following line of code in the OnRun trigger:

    ChangeCustomerName(Text001);
    
  4. Press F9 twice.

  5. Go to the following line of code in the OnRun trigger:

    VALIDATE("Post Code");
    
  6. Press F9 once.

  7. Your window should look like the following screenshot:

  8. Save and close the codeunit.

  9. From the Tools menu in the NAV client select Debugger | Active (Shift + Ctrl + F11).

  10. Run the codeunit.

How it works...

When running the debugger on this codeunit, it should stop on Customer.VALIDATE("Post Code") line of code. This is because we have set a breakpoint here, which was the filled-in red circle at the left of that line. The debugger stops right where we tell it to, that is right before that line of code executes...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image