Our payroll employee took it upon herself to run the Year-End File Reset and copy files to history and THEN decided to ask me if she could run it.
I said no, of course because we had to do backups and run the year-end tax update, and before that I needed to install the latest GP servicepack.
I came in on the weekend to do this, and realized she had started the year-end process, and then killed the job when I told her not to run it.
Some files got copied over to history, but it appears that all of 2004 is still in the current tables. I called our vendor and they hate it when I say "restoring from backup is not an option". They suggest deleting the 2004 data from history and trying it again.
Here are the tables I'm clearing data from:
CPY50100
CPY50101
CPY50107
CPY50108
CPY50140
CPY50150
CPY50160
Backup before and after and then run the year-end. Can anyone see anything terrible that might happen to us??? We have to run payroll today.
Thanks!!!
Thanks!
Barb E.
I said no, of course because we had to do backups and run the year-end tax update, and before that I needed to install the latest GP servicepack.
I came in on the weekend to do this, and realized she had started the year-end process, and then killed the job when I told her not to run it.
Some files got copied over to history, but it appears that all of 2004 is still in the current tables. I called our vendor and they hate it when I say "restoring from backup is not an option". They suggest deleting the 2004 data from history and trying it again.
Here are the tables I'm clearing data from:
CPY50100
CPY50101
CPY50107
CPY50108
CPY50140
CPY50150
CPY50160
Backup before and after and then run the year-end. Can anyone see anything terrible that might happen to us??? We have to run payroll today.
Thanks!!!
Thanks!
Barb E.