RFX_Date alternative

. In an earlier article Claude Turner has pointed out that RFX_Date does not handle invalid dates properly. This code is basically a replacement for RFX_Date that can handle invalid dates but still has the limitation that it can handle the year upto 2038 only.

In the topic: "Database Programming"-'look subject of the message' there is the remark to do not use CTime (its true), but TIMESTAMP_STRUCT (not an object) in Access ODBC programming instead. In my programs I use COleDateTime (prima!), and just the following code must be supported to handle field exchange:

void RFX_DateTime( CFieldExchange* pFX, 
      const char* szName, COleDateTime& value )
{
      CTime tm = CTime((value.GetYear()<1970 ? 1970 : value.GetYear()),value.GetMonth(),
      value.GetDay(),value.GetHour(),
      value.GetMinute(),value.GetSecond());
      
      RFX_Date(pFX, szName, tm);

      value.SetDateTime(tm.GetYear(),tm.GetMonth(),
      tm.GetDay(),tm.GetHour(),
      tm.GetMinute(),tm.GetSecond());
// instead of RFX_Date(pFX, szName, value);
}
Of course it does not exceeds date limitations of CTime bottleneck, but user has COleDateTime object with all its' functionality for 'near future' (till 2038).



Comments

  • how define time field in DAO and how write date of system on that field

    Posted by Legacy on 03/02/2003 12:00am

    Originally posted by: ASHKAN

    Dear sir,
    I create a *.mdb file with DAO but I can not write date of system in one field of database record. In other word I dont know how define time field in DAO and how write date of system on that field.Please help me with a source file
    thanks in advance,
    sincerely yours,

    Reply
Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Today's agile organizations pose operations teams with a tremendous challenge: to deploy new releases to production immediately after development and testing is completed. To ensure that applications are deployed successfully, an automatic and transparent process is required. We refer to this process as Zero Touch Deployment™. This white paper reviews two approaches to Zero Touch Deployment--a script-based solution and a release automation platform. The article discusses how each can solve the key …

  • Live Event Date: February 11, 2015 @ 1:00 p.m. ET / 10:00 a.m. PT New computing platforms, expanding information environments, recurrent security breaches and evolving regulatory frameworks are factors that security executives must contend with and address when developing their security strategy. In response to these dynamics, security executives are seeking stronger, more nimble and more pervasive security technologies to help protect business-critical information from unauthorized disclosure, loss or …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date