Grind last 7 Days

-To grind January 12, 2009:
%IBERDIR%\bin\grind.exe /date 20090112

If you are using quickservice, use grindq.exe instead of grind.


If you want to know the full grind arguments, then run:
grind.exe /? or for quickservice:
grindq.exe /?

Depending on the version, you should also have access to Regrind Subdirectories under Utilities. I think it came out in the late 5.2s or early 5.3s.

It tells you what version each dated sub is and regrinds them for you. It doesn't matter if they don't need a database upgrade. It also regrinds as far as I know.

If this is something you want to auto run once per week and you want it to automatically know what dates to run, I have some batch logic that grabs the current date and time and parses the month, date and year into separate variables. You may be able to use it to automatically determine the date and enter the command for you going back 7 days.

Not sure why anyone would need to do this unless you are needing to access the grind files for custom reporting -But if you can write your own reports or program to utilize them, you probably already know how to do this.

Alexander, what is the need for this?

Actually is for a realtime Time Attendance interface. I upload adjtime.dbf and gndbreak.dbf to a server using RSYNC where the Payroll soft import employees clock in and tips data. Because manager do some sort of editing in back of the house server I need to grind files... because when a clock in is edited Aloha create a temporary ADJTIMEX.DBF (note not ADJTIME.DBF) File that the grind process convert to ADJTIME.DBF. At end of day one of the checkpoint of the process is updating this adjtimeX.dbf to adjtime.dbf. So because i want to have the latest clock in information edited (Manager had until Saturday 3PM to edit) I grind the last 8 dated subdir at 3:05PM and upload them to the server.

Actually i had a batch script that take care of this. I only wanted to know if there was a parameter in grind.