Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Convert string to Date Time

Posted on 2004-03-27
11
Medium Priority
?
596 Views
Last Modified: 2010-04-05
I am reading a date field 'mm/dd/yy' from a table.  I need to be able to perform calculations on it to determine if it is older than 90 days.  When I pull it from the table using the .AsDateTime, it comes back with the value '0'.  However when I convert it to a string, it works fine and displays the date.  I am assuming this is because my date is not formatted correctly including the time 'MM/DD/YY HH:MM:SS.'  Is there a way I can get around this and just store and work with the date only?  

verifiedDate := Form1.tblAgents.fieldbyname('EmailVerified').AsDateTime;
strVerifiedDate := DateTimeToStr(verifiedDate);
 
 
0
Comment
Question by:jennifere
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
  • 2
  • +2
11 Comments
 
LVL 11

Expert Comment

by:shaneholmes
ID: 10695395

It shouldn't be zero, place a condition break here

--> verifiedDate := Form1.tblAgents.fieldbyname('EmailVerified').AsDateTime;
      strVerifiedDate := DateTimeToStr(verifiedDate);

then run, and when it breaks there, place mouse over verifieddate, look at the hint, see if it shows its value.

Shane


0
 

Author Comment

by:jennifere
ID: 10695513
I did place a condition break there-  this is how I determined the value '0'.  I have no idea why it is saying 0.  I checked the field in the table and it is '12/30/03'.

Basically- I'm at this point.  I have the date stored as a string value: strVerifiedDate.  I just need to find a way to convert this string to a date.  I have tried 'verifiedDate := StrToDate(strVerifiedDate);' but I am having no luck..
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
LVL 12

Expert Comment

by:esoftbg
ID: 10695609
try this:

function  Str_To_Date(DS: string): TDate;
var
  D:      Word;
  M:      Word;
  Y:      Integer;
  I:      Integer;
  DT:     TDate;
  SD:     string;
  SM:     string;
  SY:     string;
begin
  DT := 0;
  try
    SD := Copy(DS, 4, 2);
    SM := Copy(DS, 1, 2);
    SY := Copy(DS, 6, 2);
    Val(SD, D, I);
    Val(SM, M, I);
    Val(SY, Y, I);
    DT := EncodeDate(Y, M, D);
  finally
    Result := DT;
  end;
end;

procedure TForm1.Button1Click(Sender: TObject);
var
  DT:     TDate;
begin
  DT := Str_To_Date('03/27/04');
  ShowMessage(FormatDateTime('MM/dd/yy', DT));
end;

emil
0
 
LVL 12

Expert Comment

by:esoftbg
ID: 10695617
Excuse me but replace
>   DT := EncodeDate(Y, M, D);
with
      DT := EncodeDate(2000+Y, M, D);
0
 
LVL 12

Expert Comment

by:esoftbg
ID: 10695632
and:
>    SY := Copy(DS, 6, 2);
with
    SY := Copy(DS, 7, 2);
0
 
LVL 11

Accepted Solution

by:
shaneholmes earned 1000 total points
ID: 10695664
Your value is not zero, believe me. If it was 0, then

 DateTimeToStr(verifiedDate);

would give you 12/31/1899

and its not, its giving you your value

try this

var
 hrs, mins, secs, msecs: Word;

 DecodeDate (verifiedDate, Ahrs, Amins, Asecs, Amsecs);

 now look at this values during a break

this should verify that verifiedDate is not zero

Shane
0
 
LVL 11

Expert Comment

by:shaneholmes
ID: 10695712
also try doing this as well

var
 DT1: TDateTime;
 
 DT1:= EncodeDate(StrToDate('12/31/1899'),AHrs, AMins, ASecs, AMSecs);
 
 if verifiedDate > DT1 then its not zero!

Shane

 
0
 
LVL 17

Expert Comment

by:mokule
ID: 10695724
Shane
May be it is clear may not to sombody but checking verifiedDate should be done after excecution of the assignment
verifiedDate := ....
0
 
LVL 11

Expert Comment

by:shaneholmes
ID: 10695911
right, i assumed jennifer would step through at least one line past the break, i guess i should have been more clear about it... thanks for waking me up - <SMILE>

Shane
0
 

Author Comment

by:jennifere
ID: 10696107
Oops... I was looking at the wrong field.  My date field actually says '12/30/1899'.  Maybe this is explains it....    Thanks- that makes sense now.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Have you ever had your Delphi form/application just hanging while waiting for data to load? This is the article to read if you want to learn some things about adding threads for data loading in the background. First, I'll setup a general applica…
In my programming career I have only very rarely run into situations where operator overloading would be of any use in my work.  Normally those situations involved math with either overly large numbers (hundreds of thousands of digits or accuracy re…
In this video, Percona Solution Engineer Rick Golba discuss how (and why) you implement high availability in a database environment. To discuss how Percona Consulting can help with your design and architecture needs for your database and infrastr…
In response to a need for security and privacy, and to continue fostering an environment members can turn to for support, solutions, and education, Experts Exchange has created anonymous question capabilities. This new feature is available to our Pr…
Suggested Courses

670 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question