Why after a recent upgrade attempt is Toad now giving access violation read errors?
One possible answer is an invalid attempt to upgrade – it’s a common problem where people get read violations after upgrades when they do not follow standard upgrade procedure. For example unzipping a beta into a production directory to get a free upgrade will cause a read error. Likewise, trying to use a trial download install to upgrade results in a similar error. Please verify that you went to support.quest.com, logged into your technical support account, that you were current on your maintenance (i.e. paid for upgrades), and downloaded a commercial version of the software install.
