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,822 of 10,840    |
|    Raoul Watson to John Smith    |
|    Re: AdoDc control peculiar problem    |
|    11 Jan 06 02:30:31    |
   
   From: WatsonR@IntelligenCIA.com   
      
   T H A N K S !! John. I appreciate it very much.   
   I didn't know how to completely discard the error,   
   your solution is perfect for my problem. thanks again.   
      
   "John Smith" wrote in message   
   news:43c398f8$0$10672$afc38c87@news.optusnet.com.au...   
   > The error is not thrown that's why you are not seeing it there it is   
   > displayed by the adodc   
   >   
   > put this in the adodc_error event thandler   
   >   
   > fCancelDisplay = True   
   >   
   > and it will stop the error being displayed   
   >   
   > "Steve Gerrard" wrote in message   
   > news:fsOdnbnDxd6EsF7eRVn-vg@comcast.com...   
   > >   
   > > "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