Cor Ligthert <(E-Mail Removed)> wrote:
> I think it is better as you ask question like this next time in the
> newsgroup
> microsoft.public.dotnet.languages.vb
Why? It's an ADO.NET question.
> However working with dates did look for me as well very complex, however the
> possibilities are endless.
>
> dim wp as string = Now.toString("dd-MM-yyyy")
>
> gives 21-05-2004
>
> http://msdn.microsoft.com/library/de...ary/en-us/cpre
> f/html/frlrfSystemDateTimeClassToStringTopic.asp
>
> Ma nadzieje, ze to pomoze?
I think you've missed part of the point of the question, which is
whether the RowFilter expression's format is *always* meant to be in US
format (as #MM/dd/yyyy#) or whether it depends on culture. I suspect
it's always meant to be in the US format, given the documentation, but
it's not clear.
There's also the question of how times should be represented, as that
isn't covered (as far as I can see) in the documentation.
Basically the DataView.RowFilter/DataColumn.Expression etc
documentation is significantly lacking - but then, I believe the
mechanism is pretty significantly lacking in the first place, as it
would make a lot of sense to *also* allow row filters, computed
expressions etc to be written in actual code rather than just in text
expressions. I haven't checked whether or not this will be available in
ADO.NET 2.0, but I'm sure I'm not the only person to want it.
--
Jon Skeet - <(E-Mail Removed)>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too