Here, we would like to consolidate a list of frequently asked questions, known issues and their resolutions/workarounds:

First, when SQLEDT encounters an unhandled exception, it shows a popup message where you should be able to click on a "View Details" button, like below.

 

If you click the View Details button, you should see more information about the issues, some of which we have tried to summarize below:

 

 

Issue 1: "Could not load file or Assembly System.Data.OracleClient" .

Resolution : This means that you are missing the OracleClient install from your .NET framework. Although you may not be connecting to Oracle Databases, we reference the .NET assembly that has the instructions to connect to it. Some versions of the .NET install do not include this by default. This can be downloaded from here
Note: This has now been addressed in 1.0.0.9. We no longer use the Oracle Client to connect, instead we now use ODBC to connect to Oracle. SQLEDT will prompt you for an upgrade the next time you start, so you should not see this anymore.

 

Issue 2: "The input stream is not a valid binary format.".

Resolution : This means that your model file has been corrupted. The easiest way to resolve this is to delete your model file, which is usually stored in your user directory\SQLEDT\Model.edtk.