Re: New Era and Y2K

Hi John, Regarding Year 2000 and Informix Products there is a DBCENTURY environment variable that could solv these problem, more details can be found on www.informix.com/informix/products/year2000.htm About upgrading from NewEra 2.12 to 3.10. I assume You are working with MS Windows 3.x on INTEL hardware platform and want to change Your software developing platform to Windows 95 or NT (3.x is a 32bit application). If You upgrade and convert code from 2.12 to 32-bit runtime You will have lots of problems! If You don't have to convert old code but can start from scratch constucting windows with the Window Painter it will be a lot easier I think! My first NewEra was version 1.00 and I have upgraded several times since then. Now I am developing under and for Windows NT4.0 with NE3.10. The last 16-bit version I used was 2.20 and this I think is also the latest (last?) version for Windows 3.x. This 2.20 version is also available on the 3.x version of NewEra and still produces a 16-bit application which hopefully could be run on a Windows 3.x runtime platform. It is also possible to run this 16-bit on Windows 95/NT but not without special treatment that is not documented! I am now waiting for the 3.11, with hopes that all the bugs I have found will be solved! /Conny email:conny.karlsson@enator.se John Clynes skrev i meddelandet <6l16fc$25f$1@starburst.uk.insnet.net>... >I'm using New Era 2.12. >I have heard it is not strictly y2k compliant. Can anyone tell me in what >way is this so. >What areas of code (dates obviously) do I need to check to make sure code is >OK. >Are there any particular functions etc that use on 2 digits for the date >(like DateSerial in VB). > >Also, can anyone inform me on how easy/difficult it would be to upgrade to >3.10. (We have custom built classes where the C is not compliant with New >Era 3.10). > >If anyone has any thoughts or experience of sorting out the above, I would >appreciate any advice. >Thanks, >John > >