Re: Handling empty relation to child object
From: OpticTygre (optictygre_at_adelphia.net)
Date: 07/23/04
- Next message: Kevin Yu [MSFT]: "RE: after .doc (word) creation it downloads the file but i want it to be opened"
- Previous message: Martin: "Re: Handling empty relation to child object"
- In reply to: Andrew: "Handling empty relation to child object"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 22 Jul 2004 21:38:03 -0400
What if you just did
Try
x = myInvoice.Client.Name
Catch
x = ""
End Try
It's essentially the same thing, but you won't have to check for Client =
Nothing. I'm not sure if this is faster than your way, though.
-J
"Andrew" <andrewt@nospam.dbasplus.com> wrote in message
news:%23pT5EM7bEHA.3864@TK2MSFTNGP10.phx.gbl...
> In a Typed Dataset, is there a way on the xs:keyref tag that I can specify
> how to handle null child objects?
>
> For example, if I have an Invoice table, where a ClientID key is used to
> create a reference to a Clients Table by it's ID Column. On the Clients
> table I have a Name element.
> In the calling code I do :
> x = myInvoice.Reference
> x = myInvoice.Amount
> x = myInvoice.Rate
> x = myInvoice.Client.Name
> this will throw an error if, for whatever reason, the Client does not
exist.
> How can I get it to return an empty string instead of having to do :
>
> If Not myInvoice.Client = Nothing Then
> x = myInvoice.Client.Name
> else
> x = ""
> End If
>
>
- Next message: Kevin Yu [MSFT]: "RE: after .doc (word) creation it downloads the file but i want it to be opened"
- Previous message: Martin: "Re: Handling empty relation to child object"
- In reply to: Andrew: "Handling empty relation to child object"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|