Cannot post to gl after printing transaction journal
Cannot post to gl after printing transaction journal
(OP)
After printing a transaction journal or general journal I get the following message "unable to update G/L transactions while a G/L report is being printed". There are no G/L reports being printed, nor are there any documents waiting to be printed by either of my printers. I would appreciate any help you can give me in solving this problem.
RE: Cannot post to gl after printing transaction journal
http://co mmunity.sa gemas.com/ sagemas/?c ategory.id =SageMAS90 and200Disc
RE: Cannot post to gl after printing transaction journal
No. There are no other windows open. It does't matter whether I print the transaction journal without previewing or if I preview and then print. I get the same message as stated in my previous post. I have printed the G/L report to see if it would clear up the problem. I was hoping there would be someone that would have a workaround to get the journals posted or someway to convince the system that the G/L report is not being printed. I have not changed any settings since I was able to print and post just a couple of days ago.
RE: Cannot post to gl after printing transaction journal
http://co mmunity.sa gemas.com/ sagemas/?c ategory.id =SageMAS90 and200Disc
RE: Cannot post to gl after printing transaction journal
It is a single user system and I have rebooted numerous times.
RE: Cannot post to gl after printing transaction journal
http://co mmunity.sa gemas.com/ sagemas/?c ategory.id =SageMAS90 and200Disc
RE: Cannot post to gl after printing transaction journal
RE: Cannot post to gl after printing transaction journal
2. Enter "GLWSJA" (without quotes) in the 'Program Name' field, and click 'OK'.
3. Click 'Yes' to purge the update from SY0CTL.
Dawn
Visit Sage's Online Community mmunity.sa gemas.com/ sagemas/?c ategory.id =SageMAS90 and200Disc
http://co
RE: Cannot post to gl after printing transaction journal
Thank you! I got this fix from a friend, a MAS90 reseller, yesterday and it fixed my problem. He said it was a locked file that caused the system to think a report was being printed.
Chuck