Re: OleDbDataAdapter appears to use incorrect path to DB
From: id (idkrome_at_hotmail.com)
Date: 02/19/04
- Next message: Jake Lee: "Installation Failure of MDAC 2.1 on Windows Server 2003"
- Previous message: William Ryan eMVP: "Re: 19 Feb 2004, How to access VB.net applications thr' PDA's"
- In reply to: Scott M.: "Re: OleDbDataAdapter appears to use incorrect path to DB"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 18 Feb 2004 20:52:11 -0800
"Scott M." <s-mar@BADSPAMsnet.net> wrote in
news:e2xqDXp9DHA.1128@tk2msftngp13.phx.gbl:
>> > No need to have your Try...Catch return nothing.
>>
>> Interesting. The reason i do this is so I exit the function and I
>> return Nothing because this will signify that the function failed. By
>> the way, I am returning a DataTable from this function.
>
> Ok, you didn't show that you had this code in a function, so I didn't
> understand why you were using Return. If your function's return type
> is seet to a DataTable, won't you error out if your return Nothing
> (which is not a DataTable)?
Yep sorry i didn't include that function.
Returning Nothing works ok. From my understanding it's like passing a
reference to nothing back.
Also, I sorted out my original problem! It was an error in the SQL select
query. However, I still can't understand why this would change the path to
the database within the Data Adapter's Select Command's connection string.
Thanks for you help.
- Next message: Jake Lee: "Installation Failure of MDAC 2.1 on Windows Server 2003"
- Previous message: William Ryan eMVP: "Re: 19 Feb 2004, How to access VB.net applications thr' PDA's"
- In reply to: Scott M.: "Re: OleDbDataAdapter appears to use incorrect path to DB"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
