GDT Where Used Tool - free of charge -

tom66tom

Analyze your NAV objects NAV 5, NAV2009, NAV2013
All objects, functions and fields will be listed.
See connection by "where used"
http://www.g-d-t.de/download.htm

tom66tom

now available:
GDTWhere Used for NAV2015 and NAV2016

tom66tom

GDTWhere Used v 1.0.0.7
fixed local variables recognized
Finsql direct import is supported NAV2015 and NAV2016

tom66tom

Update to 1.0.0.11
28/04/2016
- copy text with STRG-C to clipboard optimized
- runmodal is recognized
- font size corrected, due to the change you must reselect the font and size

Update to 1.0.0.10
13/04/2016
- direct import with finsql excludes unlicensed Objects
- new Option (select your Texttype and size for the textbox)

Update to 1.0.0.9
07/04/2016
- Fieldnumbers for Tablefields
- visuell Upgrade(Analyzer)
- supporting run with call by constants

Update to 1.0.0.8
18/03/2016
- automatic Update to newest version

Gianfranco

Just downloaded and tested for an immediate need. Easy to install and use. While waiting to see its points of strenght in future situation, I think of a possible useful improvement: tracking "where used" for a Table with the 4 main instruction (insert, modify, delete, rename).
Thanks a lot for sharing.
Great job.

www.novus.it
www.dygroup.it

vaprog

If an object has no Where Used entries, selecting the object in the tree opens the object itself. As soon as a Where Used entry exists, viewing the object itself is no longer possible from its tree entry. Could this be changed?

The first thing I do after an object's source is shown in the right pane is resizing the window, then reducing the size of the left pane, each time the app is started. Could it be made to remember its size (and position)?

Variable declarations are not listed in the where used entries. Any reason for this?

tom66tom

Gianfranco wrote: »

Just downloaded and tested for an immediate need. Easy to install and use. While waiting to see its points of strenght in future situation, I think of a possible useful improvement: tracking "where used" for a Table with the 4 main instruction (insert, modify, delete, rename).
Thanks a lot for sharing.
Great job.

www.novus.it
www.dygroup.it

Hi Gianfranco,
thank you for your comments! We will add your point to the wishlist.
best regards
tom

tom66tom

vaprog wrote: »

If an object has no Where Used entries, selecting the object in the tree opens the object itself. As soon as a Where Used entry exists, viewing the object itself is no longer possible from its tree entry. Could this be changed?

Regarding your point, to see the Object source code of the Object itself, when where used entrys are present: We will look into this, but no promises, because it could decrease the performance.


The first thing I do after an object's source is shown in the right pane is resizing the window, then reducing the size of the left pane, each time the app is started. Could it be made to remember its size (and position)?

We will remember size and postion of the window and the slider in the next version.

Variable declarations are not listed in the where used entries. Any reason for this?

The purpose of GDT Where used is, to display the connections between objects.
Variables are only accessible inside an object itself.

We keep it at this: The more information we display, the more the visual presentation and, consequently, the optical overview will suffer.
Best regards
tom

vaprog

Thanks a lot!
And so quick. Amazing.