B
Brian Candy
I am guessing that this must be a common question, but I just can't
find a simple solution for it by searching the newsgroups. I have a
Text Box with a date in a UK format. The format has been verified and
is legal. Now all I want to do is pop it into an SQL field. Debugging
on my local machine everything works with the following:
dDOB = CDate(txtDOB)
Row.Item("DOB") = dDOB
But when deployed this would fail because CDate requires MM/DD/YYYY
rather than DD/MM/YYYY.
In short I want to display and collect dates from users with the date
format DD/MM/YYYY which is fine on my local machine, but not on my
server farm. If I use string manipulation to solve this, it works on
my server farm but not on my local machine. I could write some
un-elegant code to solve this, but I am convinced there must be a
simple way of overcoming this problem.
Thanks in advance for any help.
Brian Candy
find a simple solution for it by searching the newsgroups. I have a
Text Box with a date in a UK format. The format has been verified and
is legal. Now all I want to do is pop it into an SQL field. Debugging
on my local machine everything works with the following:
dDOB = CDate(txtDOB)
Row.Item("DOB") = dDOB
But when deployed this would fail because CDate requires MM/DD/YYYY
rather than DD/MM/YYYY.
In short I want to display and collect dates from users with the date
format DD/MM/YYYY which is fine on my local machine, but not on my
server farm. If I use string manipulation to solve this, it works on
my server farm but not on my local machine. I could write some
un-elegant code to solve this, but I am convinced there must be a
simple way of overcoming this problem.
Thanks in advance for any help.
Brian Candy