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(),
      RFX_Date(pFX, szName, tm);

// 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).


  • 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,

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

Top White Papers and Webcasts

  • Anthony Christie, the Chief Marketing Officer for Level Communications, is responsible for customer experience, worldwide marketing and product management. In this informative asset, he shares his insights into why a private network connection to cloud-bases applications is the right decision for your enterprise. Download now to find out more.

  • Enterprises are increasingly looking to platform as a service (PaaS) to lower their costs and speed their time to market for new applications. Developing, deploying, and managing applications in the cloud eliminates the time and expense of managing a physical infrastructure to support them. PaaS offerings must deliver additional long-term benefits, such as a lower total cost of ownership (TCO), rapid scalability, and ease of integration, all while providing robust security and availability. This report …

Most Popular Programming Stories

More for Developers

RSS Feeds

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