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

  • When individual departments procure cloud service for their own use, they usually don't consider the hazardous organization-wide implications. Read this paper to learn best practices for setting up an internal, IT-based cloud brokerage function that service the entire organization. Find out how this approach enables you to retain top-down visibility and control of network security and manage the impact of cloud traffic on your WAN.

  • Moving from an on-premises environment to Office 365 does not remove the need to plan for disruptions or reduce the business risk requirements for protecting email services. If anything, some risks increase with a move to the cloud. Read how to ease the transition every business faces if considering or already migrating to cloud email. This white paper discusses: Setting expectations when migrating to Office 365 Understanding the implications of relying solely on Exchange Online security Necessary archiving …

Most Popular Programming Stories

More for Developers

RSS Feeds

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