Eric, I work on a genealogy project from time to time. The best solution I've found for managing dates across long time spans is to store them as strings. Either
YYYYMMDD (I used this for years) or the ISO format YYYY-MM-DD You would have to setup new fields for them and generate some utilities to manage them (I'll share mine if you are interested). Has the advantage of accommodating approximations (that's the genealogy thing). And it's easy to append the time string as well. I've never had any performance issues with this, by the way. String operations are pretty fast. On Thu, Aug 25, 2016 at 10:51 AM, Eric Naujock <[email protected]> wrote: > What am in need of doing is finding the proper year and being to define it > in mass for all the records in the database so that I have no 2 digit years. > -- Kirk Brooks San Francisco, CA ======================= ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
