Bug - Access violation using Toad 8.x SQL Editor

In Quest Software's Toad version 8.0.0.47 (SQL Editor) the ctrl+space key combination activates it's own internal inteli-sense which obviously takes precedence over SQL Assist, I have replaced the default key combination with CTRL + CAPS LOCK, however I get the following error:-

Access violation at address 08217405 in moduke 'SqlAssistPrefs.dll'. Read of address 00000000.

After Selecting OK (which is the only option) the "SQL Assistant - Connect dialog" is displayed but no servers are listed in the Server name drop down" and no OCI Homes are listed in the "OCI Home drop down".

The server name can be manually typed however the OCIHome cannot be, therefore a server connection cannot be obtained.

The Oracle Client is installed in Oracles default (Installer) location C:\Oracle\product\10.1.0\Client_1 and all connections to Oracle servers in the TNSNames.ORA file work correctly via Toad / VS2005 Server Explorer / SQLPLUS etc

SQL Asistant - Toad Target Settings
SQL Assistance : Oracle
SQL Reference : Oracle SQL 10g
Code Snippets : PL/SQL
Target Name : TOAD.exe
Target Window Class : TToadSyntaxMemo

Some good news though
In Visual Studio 2005 the default key combination works fine a SQL Server (SQLEXPRESS) connection.

Thanks for very detailed report. We will check what could be causing that. Tomorrow we will have a new build available for download. Some internal stuff has been reworked. Please try this new build just in case...

By the way, does it work with SQL*Plus?

The reason for my asking is that in SQL*Plus it intercepts the existing connection and uses it to run database lookup queries.