We are writing a VB4 server routine to access a remote SQL database via
ODBC. When connecting, we supply all the login details and password via
the ODBC string in the source parameter of OpenDatabase .
If the database is down or not responding, ODBC tries to prompt the user
for login details. This is a BATCH program though and there is no one
around the server to respond so the program just sits there!
How can we stop this prompt and get ODBC to report an error back
instead.
Do Microsoft not realise that 'BATCH' programs are still essential to
some computing solutions??
Please help if you can
Thanks Robin Benton
--
Agent Computing