How can we help you today? How can we help you today?
shadowbob
Oops! Sorry for the false alarm. It seems that object hints are indeed working. I was hovering over a TRUNCATE TABLE statement and wasn't getting any hints. I didn't realize I wasn't supposed to get any hints there. / comments
Oops! Sorry for the false alarm. It seems that object hints are indeed working. I was hovering over a TRUNCATE TABLE statement and wasn't getting any hints. I didn't realize I wasn't supposed to ge...
0 votes
Hmm, now object definition hints aren't working. With or without the "workaround" above. This is turning out to be a bad day for Prompt. Are they working for you? (It's the "hyperlink" when you hover over a name.) / comments
Hmm, now object definition hints aren't working. With or without the "workaround" above. This is turning out to be a bad day for Prompt. Are they working for you? (It's the "hyperlink" when you hov...
0 votes
The option you mentioned is indeed turned off. Would turning it on solve my problem? I'm curious why you would ever be able to drop an assembly without first dropping it's dependent objects. Thanks. / comments
The option you mentioned is indeed turned off. Would turning it on solve my problem? I'm curious why you would ever be able to drop an assembly without first dropping it's dependent objects. Thanks.
0 votes
I recently used Dependency Tracker for the first time, and my primary issue with it was similar to this thread. Let me describe my situation and what I was looking for; perhaps this will help focus the discussion. When I need to do a dependency analysis, it involves not just the database but also other source code in various projects. This requires me to do multiple analyses in various manners and merge them into a central dependency tree. I create this tree as an Excel spreadsheet, which I then pass to my team to work on. Dependency Tracker would be the ideal tool to perform the database portion of this analysis. The issue I ran into, however, is that there is no easy way to get the list of dependent objects out into Excel. Once I've brought up a diagram in Tracker, I just need the Type and Name of every dependent object. Preferably, I'd like to be able to just copy this list into the clipboard, and have it tab-delimited so it will paste into Excel as two columns. If not that, then I at least need a plain-text export. Again: I just need the list of dependent objects, not what their relationship is, or any other metadata beyond the type of object. Tracker is not very useful to me until this kind of thing can be done easily. As it was, I had to manually retype the name of every object into my spreadsheet. Not the ideal situation. The final piece to this would be creating an easy way to select just the objects that are dependents, and not select the original objects that I placed in the diagram for analysis. I already know what those objects are -- I don't need them any more. Hope it helps! Thanks for another great tool. / comments
I recently used Dependency Tracker for the first time, and my primary issue with it was similar to this thread. Let me describe my situation and what I was looking for; perhaps this will help focus...
0 votes