Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.visual.basic    |    MS Visual Basic discussions, NOT dot-net    |    10,840 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 9,816 of 10,840    |
|    Steve Gerrard to Raoul Watson    |
|    Re: AdoDc control peculiar problem    |
|    09 Jan 06 19:42:35    |
   
   From: mynamehere@comcast.net   
      
   "Raoul Watson" wrote in message   
   news:wOEwf.1807$JT3.1534@trndny06...   
   >I have a form with an AdoDc control associated to a datagrid.   
   > The AdoDC uses a "ConnectionString" such as   
   > "Provider=Microsoft.Jet.OLEDB.4.0;Persist Security Info=False;Data   
   > Source=..."   
   >   
   > this is where the problem begins. The data source will not be known until   
   > the user selects the database.   
   >   
   > What is really weird is that if the source is not placed during design time,   
   > during run time the form upon loading will generate an error ("Failed to   
   > authenticate"). This error seems to be untrappable since it doesn't occur in   
   > the Form Load or Activate event (I have tried to catch it there).   
   >   
   > Of course once the error is ignored and the datasource is set in the form   
   > load, everything works OK.   
   >   
      
      
   You should be able to start the app without an error if the connection string   
   property of the ADODC control is completely blank. Then set the entire   
   connection string in code, including the part about "Provider=" etc.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   
|
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca