🚀 go-pugleaf

On 23/09/2006, Clayton Arends wrote:

> The only function that causes the AV in this test application is the 
> "Create" function.  If I make no other changes to the application and
> simply wrap the Exec() call in a try..catch block then the app
> executes correctly.  It even executes other code in the try area
> which means it's not throwing anything.  Example:
> 
>   // Create the database
>   vCatalog=Variant::CreateObject("ADOX.Catalog");
>   try
>   {
>     vCatalog.Exec(Function("Create") << strConnectionString);
>     printf("1\n"); //<-- this prints
>   }
>   catch (...)
>   {
>     printf("ouch!\n"); //<-- does not print
>     throw;
>   }
>   printf("2\n");
> 
> I don't believe this is the solution but it is interesting.  I'm
> going to perform some more searches in Google.

Thanks for looking into this. I agreee that this is not the solution,
but hopefully it's iterating toward a solution.

You mentioned in an earlier post that this is more a "VB" solution. I
was advised when starting out on this, that this was closer to the
underlying "bare metal" of the way that MS Windows handles ADO, and
therefore I'd experienece less problems and issues. Is this perhaps not
the case?

I wonder if my prerequistes for mulithreading
CoInitializeEx(NULL, COINIT_MULTITHREADED);
is incorrect. The app which ultimately uses all of this is heavily
multithreaded so I want to make sure that mulithreading support is
enabled.


-- 
Simon Elliott    http://www.ctsn.co.uk