what should pfcmark be set to with oldest invoice date in 1992?

[Nancy Palmquist]

Jose,

Remember this will also apply to data entry.  If you have a date field 
defined at 10,mdyy/ and the data entry person types:

6/1/22

Do you want filepro edits to make that 06/01/1922 or 06/01/2022?  We see 
this in my software when entering birthdates which can often be more 
than 100 years back these days.  We set PFCMARK to try to get the 
longest range back, since this is a critical date.  So we set PFCMARK = 
20 - at the low end.  Of course, this means you have to scoot it forward 
more often.  The birthdate is stored as 10,mdyy/ but it makes data entry 
quicker.

For accounting, it is unlikely most computers have stuff older than 1980 
so you can certainly set that PFCMARK as a much higher number such as 
80.  This allows data entry to accept the year as 2 digits and convert 
it properly to 4.

Another thing to remember is to us @t4 for a default date instead of 
@td.  @t4 is not affected by PFCMARK but @TD is so if you are loading a 
data field with a date stamp try to opt for @T4 whenever you can in 
processing.

Just my thoughts on the subject.  I have converted a number of systems 
that had issues since Y2K and it is not always necessary to change every 
date field to 4 digit years.  But you have to be wise about your use of 
dates.  I think when the customer sees a 4 digit year they are more 
comfortable that the dates are working correctly.

Indexes built on date fields might especially be affected by PFCMARK 
issues so it might be best to make those 4 digit years.

Last, if your programming is still in play in 2080 when the PFCMARK 
needs fixing, I say congrats to you.  I am surprised I have customers 
with software written in 1980 still running said software, but I do not 
expect that continue for 10 years.  Technology will overtake the system 
they use now and needs will change.  The people at the company that 
designed and built the system will retire and the new people will only 
want Microsoft solutions.  I see it already with new employees.  They do 
not understand the value of custom applications, they want spreadsheets, 
instead of reports. ( Not impossible but I can process data much better 
in filepro than dumping to a file so they and tweak it in a spreadsheet.)

IMHO
Nancy

On 12/5/2016 10:57 AM, Jose Lerebours via Filepro-list wrote:
> On 12/05/2016 10:52 AM, Kenneth Brody via Filepro-list wrote:
>> On 12/5/2016 9:59 AM, Walter Vaughan Jr via Filepro-list wrote:
>>> Actually unless you are running true 64 bit binaries I would think 
>>> everything *nix based breaks 03:14:07 UTC on 19 January 2038
>>
>> That only affects the current system time.  It has no effect on 
>> filePro dates.
>>
> Ken, if one uses mm/dd/YYYY or YYYY/mm/dd, does filePro still need 
> PFCMARK in order for other date related methods to work?  Say for 
> example, date math, doy(), dom(), dow() ... !?!
>
>

-- 
Nancy Palmquist         MOS & filePro Training Available
Virtual Software Systems    Web Based Training and Consulting
PHONE: (412) 835-9417           Web site:  http://www.vss3.com