Conversion from string "18/8/2009" to type Date is not valid...

[Lost User]

Johnkokk wrote:

Does it make sense to you ?

Not exactly; your title says you are converting from the string "18/8/2009", but your code is converting something ToString(). Can you clarify a bit more what is in dgv1(0,counter)?

[Johnkokk]

The field of the datagrid contains "18/8/2009".This is a string. I am trying to get the month part of this date. On my computer whatever i try WORKS. On the other PC whatever i have tried, DOES NOT. Even if i don't put the .string, DOES NOT work on the BETA tester. To make it simple.How do i get the month part of the above field to use as an index in an array ?

[Johnkokk]

Τhe problem seems to be the regional setting of the other pc, which are different than mine.If they are change to the same as mine, it works Hmmmmm

[TheDudeJuan]

you could split the string ( string.Split() ) and then take the second index of a string array, then you have the number of the month, maybe you could work with that?

Here we rest... So why not make the best of it? :D

[Luc Pattyn]

it seems you don't have a clue. the only thing that could go wrong in tempor=Month(dgv1(0, counter).Value.ToString) is a NullReferenceException due to dgv1 or Value being null. if there is a problem, it is bound to be in a different line. Look at the entire exception.ToString() output, tell your IDE to show line numbers, and get the line at fault. Most likely it is about date formatting. The first thing about it is you have to decide whether you want a user-selected format (through Regional Settings), or a fixed format (specified explicitly in your conversions, see the Parse/TryParse method overloads that take explicit format info). :)

Luc Pattyn [Forum Guidelines] [My Articles]

---

I only read code that is properly indented, and rendered in a non-proportional font; hint: use PRE tags in forum messages

---

[Mycroft Holmes]

Your problem is that you are storing your dates as strings. THIS IS WRONG AND VERY STUPID. This is error number 1 when a newbie starts working with dates. You should IMMEDIATELY go back and change your date storeage and manipulation from string to datetime. Dates are subject to the computers cultureinfo, this means if the user has not changed the culture of the computer from the default american format (stupid friggin mm/dd/yyyy yank format) your 18 is being read as a MONTH, If it was a datetime format you would not have this problem.

Never underestimate the power of human stupidity RAH

[Johnkokk]

Although i am not exactly newbie at programming, i admit i am relatively new to .net framework thing. As i said on my second post, the problem was indeed the regional settings.The user had set them to American, and so it was reading 18 as Month, thus the error. The reason i didn't use datetime in the field, is because the data are stored in a MS ACCESS database, and it was giving all sorts of problems trying to use the field.So many different bugs i don't even remember. So i made them strings. However i might give it one more shot to see what happens.

[Lost User]

I would concur with the comments from Luc & Mycroft. Do not store dates and times as strings, it just leads to exactly this sort of problem. A DateTime value is universal and can be displayed in whatever format is required, and in many cases converted to a non-Gregorian calendar.

[Lost User]

Not a good answer, study DateTime structure.

[Mycroft Holmes]

Johnkokk wrote:

However i might give it one more shot to see what happens.

I would strongly recommend trying. You will almost certainly run into malformed dates already in the field which will produce error but then you will be fixing your data :)

Never underestimate the power of human stupidity RAH