C#

Dio22 wrote:

"Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

ForkOffandDie wrote:

if calling Dispose() results in an implicit call to Close()

try
{
    if (table != null)
    {
        OleDbConnection connection;
        try
        {
            connection = new OleDbConnection();
            connection.Open();

            OleDbCommand command;
            try
            {
                command = connection.CreateCommand();
                command.CommandText = "SELECT obj From " + table.Alias;

                OleDbDataReader reader;
                try
                {
                    reader = command.ExecuteReader();
                    while (reader.Read())
                    {
                        container.Add(new Feature((xx)reader.Getxx(0)));
                    }
                }
                finally
                {
                    if (reader != null)
                    {
                        ((IDisposable)reader).Dispose();
                    }
                }
            }
            finally
            {
                if (command != null)
                {
                    ((IDisposable)command).Dispose();
                }
            }
        }
        finally
        {
            if (connection != null)
            {
                ((IDisposable)connection).Dispose();
            }
        }
    }
}
catch (Exception)
{
    MessageBox.Show("There was a GPS Error");
}

1. The runtime searches the array for the first protected block that:
   
   • Protects a region that includes the currently executing instruction, and
     
   • Contains an exception handler or contains a filter that handles the exception.
     
   
   
2. If a match occurs, the runtime creates an Exception object that describes the exception. The runtime then executes all finally or fault statements between the statement where the exception occurred and the statement handling the exception. Note that the order of exception handlers is important: the innermost exception handler is evaluated first. Also note that exception handlers can access the local variables and local memory of the routine that catches the exception, but any intermediate values at the time the exception is thrown are lost.
   
   
   If no match occurs in the current method, the runtime searches each caller of the current method, and it continues this path all the way up the stack. If no caller has a match, the runtime allows the debugger to access the exception. If the debugger does not attach to the exception, the runtime raises the UnhandledException event. If there are no listeners for the UnhandledException event, the runtime dumps a stack trace and ends the program.

ForkOffandDie wrote:

What would have priority over a thrown exception such that it HAD to process before a catch was allowed to handle the Exception?

Pete O`Hanlon wrote:

ms.Position = 0;

Luc Pattyn wrote:

Hi,

AFAIK an RTB is capable of showing an RTF file, which you can generate with either an RTB or
with Wordpad. An MS Word document (.doc) can not be loaded into an RTB.