by We have a VB4.0 application that interfaces with a Access DB using DAO
(Jet) running on a NT 4.0 Server with SP 1 installed. We have linked
tables that sit in a SQL 6.5 Server on another machine in the same
domain.
When accessing the tables we connect to the SQL-Server setting the
correct CONNECT information.
This works fine, as long as the login is sueccessful. If it fails, or if
it breaks during data-access, we get a VB-Popup-Woindow asking for a new
ODBC-login User-ID. Since the application runs unattended the applic
stops showing this popup. This is a major problem for us.
How can I avoid this?
There should be an Option NOPROMPT when accessing a DAO-Object that is
linked throug ODBC...
Your help is very much appreciated.
Please reply by mail as well..
***********************************************
* CITYLINE AG www.cityline.ch *
* 8005 Zurich / Switzerland *
* Tel: +41 1 273 37 40 Fax: +41 1 273 37 47 *
***********************************************
--
***********************************************
* CITYLINE AG www.cityline.ch *
* 8005 Zurich / Switzerland *
* Tel: +41 1 273 37 40 Fax: +41 1 273 37 47 *
***********************************************