Dates returning /OV for year

[julianm]

Users are receiving /OV on date of birth year and transaction dates. Anyone else having this issue? I guess its due to the new year.

[julianm]

Thank you Bill for the solution.

my pfcmark was set to 10 in Filepro Configuration editor, increasing the value to 30 fixed the issue and dates are printing fine.

[Joe Chasan]

Interestingly, i had a call from a customer with same issue yesterday - dates (in my case, specifically @td) that were 8,mdy/ would go to /OV (those of 10,mdyy/ were ok) - this was a 5.0.14 install that predates my involvement on-site.  Changed PFCMARK to fix - note you should rebuild any indexes based on date that are not 4-digit years after changing.

I wonder if 10 was the default PFCMARK on DOS/WIN/Network installs - Bill?

[julianm]

rebuild index? I'm very new to FP and wondering if this is something I should do. We have issues with transaction reports by date that are not printing. It displays reading keys and sorting then gives an error index to big would you like to create a smaller one.. this is on version 5.0.11 on a linux box. This was after changing the pfcmark.

[Bill Randall]

10 was and still is the default.  It is however changable at installation.  It is also read from the config file so that if doing an upgrade the install will read and display what the customer has already set it to be.

Any indexes built on dates would require rebuilding after a pfcmark error.