Do a ctrl-click into the object instead. You can float the editor if you want it to behave like DESC popup.
ctrl-click on the table name pops a message saying the PL/SQL <<table_name>> does not exist
Code samples always help.
ok, say my table_name is ACCOUNTS.
I have a sql statement like the following
I put my cursor on ACCOUNTS the ctrl-click. the message "PL/SQL unit accounts does not exist" pops up
and that is true, ACCOUNTS is a table, no a PL/SQL object. I use the F4 key in TOAD hundreds of times (or so it feels) a day to review table structure and data. the simplistic sql statement above is nothing like the code that I nomaly have in from of me that make the F4 function so helpful in TOAD.
sorry about the spelling, typing in a hurry :/
what version of the tool are you using?
Is accounts actually a synonym for a table somewhere else, or I can assume it's in the same schema as your login user?
in the example above ACCOUNTS is the actual name of the table and it is in the schema that I am logged into.
Sounds like a bug, but 'it works for me' - which I know is not useful.
Let's see if it works at all.
Can you try in a blank worksheet, with nothing else, something like:
select * from scott.emp; or
select * from hr.employees;
For your accounts table, does the code insight feature work? For example, delete the * or add a where clause - can you get a list of columns to popup?
I typed apps.FND_REQUEST into a blank worksheet and did the ctrl-click and it worked. I just need to figure out how to get that to work on a table. will try what you suggested
click works. the accounts table that I was using to test (being the first table in the list) turned out to be the problem. even though i could click on it to get it in edit mode. if i tried to exec the
select * from accounts i get a table not found. so i tried another table and it worked.
Thank you vary much for you time, and sorry for the run-around.
i spoke too soon. it only works on some tables not others.
ok, so i can't just have the table name in the editor window alone. i has to be in a sql statement to work
Correct, it's about context. We don't blindly slam the data dictionary querying for any and everything - we use the parser to determine if you have a proc, view, user, etc.
If you're in v4.0, I also recommend you check out Alt+G - it fires off a database object search for the word at the cursor, or whatever is highlighted. It's wicked fast, and you can click into the objects it finds in the results. I have a video/blog post on that too if your'e interested.
alt-G is exactly what I was looking for!