ActiveX DLL to ActiveX EXE
> Use an event object to tell the other process when to terminate (see
> platform sdk "CreateEvent").
> Also, if you are using ADO, set a connection timeout so that you don't
> get locked in a call to the database.
> For more detailed responses, form more detailed questions.
> > I have an app that passed data to a remote SQL server, the problem
however is that the
> > SQL server may not be available at all times and this slows down my
> > what I have done is moved the number crunching section into an
ActiveX DLL as a set of
> > functions and the section of code that speaks to the server into an
out of process
> > ActiveX EXE, the problem is that the app is still waiting if the SQL
> > is not available.
Activex DLL or ActiveX Exe will not make a difference here.
You didn't say if you were using DAO, RDO or ADO. You also didn't say if
the SQL Server
could disappear after you opened a connection to it or if you don't
always expect it to be
there when you want to open a connection.
All of them have requisite LoginTimeOut and QueryTimeOut properties (in
You could also look into executing your queries asynchronously. I hope
catching the error with the first SQL statement that determines that the
server is AWOL. And I hope you are not firing any more SQL statements
catch this error.
Please reply to the group.