This content has been marked as final. Show 2 replies
Is that really true? For which versions?
Using 3.2.2, I tried opening some pks/pkb files and got the Code editor, not the Worksheet editor. Perhaps your user settings got corrupted somehow. You might try the usual technique of ...
It actually is possible to edit one of the preferences.xml files to force the pks and pkb extensions to use the Code editor (except I forced them to use the Worksheet editor in my test), but I believe the best (supported) approach is to reset the user settings first.
a. Export your connections and exit SQL Developer b. Delete (e.g., on Windows 7) the C:\Users\<username>\AppData\Roaming\SQL Developer\systemn.n.n.n.n folder for your version. c. Restart SQL Developer.
SQL Developer Team
Well everithing works fine on my installation. We recognized the problem on a newly installed system with 3.2.10.09 at a collegues workstation. The interesting thing is starting SQL Developer the next day, everything worked out fine. So for me the problem is solved, although I don't understand why these options are disabled in the UI.