When opening the EDIT Windows, Manually, when set to Auto Open on Connection,
or even opening without a connection, I am getting Access violation....
The contents from the "click here" is as follows... Attached...
Toad.el (1.4 MB)
Also appears to happen, when you open any Object that would load into a Editor Windows/Tab. So Double click a Package, or Procedure, etc....
And then continues to give an error when you switch between the Tabs....
I do notice that , after clicking OK to continue,
the windows opens but the "Navigator" is not populated, until you Close and reopen it...
IE, after initial open of Windows/Tab...
Close/open Navigator......
I have a feeling it it nothing to do with connectivity, as I get the error when opening a Editor Window without opening a connection to a database...
Hi Sean. I made some changes in the Editor to create the lower tabs and navigator as needed, as opposed to when the Editor first opens, in an attempt to save resources and get the Editor to open faster.
We tested it pretty thoroughly but I kind of expected a few of these.
There are about a half dozen files with a .lay extension in your User Files folder. They contain info on where you've got all those dock panels positioned. Can you those files to me? John.dorlon@quest.com
The easiest way to get to user files folder is by clicking here in Toad Options:
Thanks for reporting this
john
I can't reproduce this, but I'm making a change for Monday's beta based on what I see in your Toad.el. Please still send your .lay files though when you can though.
You can probably solve it by right-clicking on one of the lower editor tabs (or the bluish bar above the navigator) and choose "Restore desktop defaults". But do this after sending me those files, as it will reset them.
Thanks
Thanks for your file. I can reproduce the problem and will fix it.
I see that "restore desktop defaults" just causes the error again. Instead, you can just delete all those "Lay" files from your User Files folder (do this while Toad is not running). Toad will re-create them from scratch and the error will disappear.
