Forum Replies Created
-
AuthorPosts
-
MSchapplerModerator
I suggest that you run Database Utilities from the NewViews 2.0 menu and select your application database and click the All Checks button. If problems are detected, then run Database Utilities again and select Reorganize Database.
Are you selecting a Payrun from where you had previously ran your last Payrun? If so, check the Paylist button for the employees to be paid. Review the settings for the Payrun. Perhaps there is a setting or an employee in the Pay List that is causing the behaviour you have described.
Regards to All,
Martin
MSchapplerModeratorDo you receive a window prompt to Creat a new desktop for folder /REPORT/PR?
I have tried this in NV2 version 2.16.3 which is the current NV2 version and I did get a unique desktop.
After perform the script, is the desktop report unique from your other desktop reports?
Regards to All,
Martin
MSchapplerModeratorSet the amount column width to 10 – currently your Amount column width (Line 9) is blank. Set it to 10 and this bug error can be avoided.
You are using an older version of NV2. The current version of NV2 is 2.16.3 and I suggest that you update to it after performing nvreorganize on your application databases.
If you receive a bug error, submit the bug error to support@qwpage.com – Do not post your bug errors here in the NV2 Forum.
Regards to All,
Martin
MSchapplerModeratorDo you receive an error message? Which folder or sub-folder are you running this in the Explorer tree to the left?
Regards to All,
Martin
MSchapplerModeratorGo to your Payroll Withholdings report and select Accounts > Setup. Set the employee withholding accounts under the ledger indexed columns to Yes. They are currently blank. Once the ledger indexed is set to Yes then run T4 Summary again.
This problem was corrected in the latest service pack of 2.16 which is service pack three. I suggest that you download and install it on your system(s).
Regards to All.
Martin
MSchapplerModeratorI understand your concerns. I need to know how to break the account history in service pack three of 2.16 to prevent it from happening again.
I will attempt to break the account history on my own and provide a fix when I fully understand how to break the account history in 2.16.3. If you have any insight in how to accomplish this, it would be much appreciated.
Regards to All,
Martin
MSchapplerModeratorIf there is a problem with the account history you do not need to perform a full nvreorganize. You can use Database Utilities > Reorganize > Account History.
Can you explain how you are able to damage the account history in 2.16.3. If I can duplicate I will make sure it is fixed in the next update to NV2. Send me an email in regards to this to support@qwpage.com.
Regards to All,
Martin
MSchapplerModeratorInstall 2.15.3 in another folder on your system after renaming your current NewViews 2.0 Menu to NewViews 2.16.3 amd perform nvreorganize on that application database.
Do you have a prior backup of the application database? Can you nvreorganize the prior backup?
Regards to All,
Martin
MSchapplerModeratorYes. There is a handy tool you can use under Tools > Create Transactions > Post Dated which you can create one or many transactions in the future based on an existing transaction.
Regards to All,
Martin
MSchapplerModeratorIt’s preference and many of the entries referencing journals BD and BP used Tools > Applt Deposits and Tools > Apply Payments from the respective journals.
If you look at the journal where the transaction was entered and review the ledger details, you have choices of reviewing the cross talking ledger via one mouse instead of using F9.
Regards to All,
Martin
MSchapplerModeratorDOS error code 16979 indicates that the K:DATAD.nv file is backup file that was created using Backup books from the NewViews shell or the datad.nv file is zero bytes.
Use Restore Books from the NewViews shell to uncompress the datad.nv file to it’s original size.
If the datad.nv file is zero then reloading a backup is the only solution.
Regards to all,
Martin
MSchapplerModeratorYes, we should have mentioned that compressed transactions were also decompressed in 2.15. We did mention summary postings but should have also mentioned compressed transactions also.
Regards to All,
Martin
MSchapplerModeratorI’ll see what can be done for an updated service pack to 2.16.
Regards to All,
Martin
MSchapplerModeratorAdd the following Paycode to the D=CPP line:
E=Y:
Change the line from:
D=CPP:
To:
D=CPP:E=Y:
This will make the employee exempt from CPP.
Regards to All,
Martin
MSchapplerModeratorGo into your NV1 books and issue /Go runProc (/GR) GETLIB and press enter. Enter the following and press enter:
nv1pd7
Once installed you can run PRTCHKS without the error.
You are using the CPA library (PD7) in other sets of books with the standard NV1 library (version 12) installed in the current books without updating the books to PD7.
Regards to All,
Martin
-
AuthorPosts