Page 1 of 1

Journal Questions

Posted: Sun Jul 02, 2006 12:15 am
by Sulk
If you decide to keep the journal file on disk it has to be moved. Whenever you open your register it will compare the date on the journal file to today's date. This is a good reason to keep the date and time on your computer correct. If the dates are the same then all transactions will be tacked on to the end of the journal. If the dates do not
match, and the last previous transaction was a "close", then the register will ask you if you wish to delete the current journal and start a new one. You may automate the deletion of yesterday's journal by using the "Journal" function in the POSCONFG.EXE program or you may have the register ask the salesperson opening the register if the journal should be deleted.Your journal file will have the extension of .JNL If you named your register file MARTHA then the journal file for your register will be MARTHA.JNL
To what I understand, I have to remove the .JNL file on both the Global and Local folders so that the sales would not be carried over to the next day. The warning that this carry-over would happen is the message "Journal was not printed, saved, or archived at the last register close and therefore cannot be erased and reset at this time" at the beginning of the day. To keep things short, the Global and Local folders should have no .JNL files every business day.

Am I understanding it correctly?

Posted: Sun Jul 02, 2006 4:55 am
by Sulk
Also...

I'm trying to simulate an opening and closing of the store by changing the date in Windows and the result wasn't as I hoped for.

I'm getting a "Journal was not printed, saved or archived at last register close and therefore cannot be erased and reset at this time" at the beginning of the Global POS even though I set the Journal to YES at "Erase & reset the journal at the start of the next day". This is when I advance the to a simulated next business day. I also get a "The journal's date and today's date do not match..." along with it.

My configuration is:

YES - Save journal to a text file as the transactions are rung
YES - Automate journal at open and close
No- Print the journal at close.
YES - Copy the journal to an additional text file at close
FILENAME.TXT - using this file name
F: to this drive
YES - Archive the journal file at close
YES - Erase & reset the journal at the start of the next day.

Option #2

Posted: Sun Jul 02, 2006 9:29 am
by Dale Harris
Sulk,

When you closed the register did you use option "2 Close / Print / Erase?"

Posted: Sun Jul 02, 2006 8:51 pm
by Sulk
Yes.

?

Posted: Wed Jul 05, 2006 6:57 pm
by Dale Harris
Sulk,

It is working here, are you still having a problem with this?

Posted: Wed Jul 05, 2006 11:35 pm
by Sulk
Still no luck.

Just an aside, the .JNL file's date doesn't change even though I kept on advancing the date. The journal configuration is the same as above. I also tried different combinations and it's still the same.

Is it possible that it's an OS issue? I am currently using it on a Windows XP OS but I have also tried it on a 98se machine. The results are the same.

There isn't a problem with the LOCAL folder after some re-installing. Am I supposed to use a different journal configuration for the GLOBAL folder?

Posted: Sun Jul 09, 2006 1:33 am
by Sulk
Since I'm running both a GLOBAL and a LOCAL folder on my computer for testing and learning DHPOS do you think that this has an effect to the Journal not deleting itself after every close?