-
Posts
-
We have what we believe to be a serious error on a set of books that we recently converted to 2.09 and decompressed. We believe the error is a date error:
it states “expected a year in the range” and quotes the DOS default and a line Number 14862. We connot locate the line, and when we review the compression folder, it appears that there are still items in this folder, although nothing else will decompress, and the lines seem to be out of sequence order. We have tried to locate the error to correct it, to no avail. The real problem seems to be that we had no indication of any errors when we converted from NV1, and have been using this set of books steadily since converting over a year ago, and have had no problems until we installed 2.09 and were required to decompress. The error is preventing viewing any cells in some of the views on the bank. Every cell indicates ERROR,today it is on the reconcile view, yesterday we had the reconcile view, but not the list view. It appears to be affecting our attempts to reconcile. We have tried to reorganize the books, but the error is still there. Since we have entered quite a bit of data since the conversion to 2.09, re installing is not a valid option. Any suggestions or help would be greatly appreciated
Thanks in advance,
John MacNeilJohn,
On the workstation where the problem is occuring, move the workstation.nv2 file that you are using (usually in the NV2 folder but check the properties of the NV2 icon to be sure) and then click on your NV2 Icon which will create a new workstation for you. Enter the server IP and press F3 under file after inserting a new row in your new workstation table. Enter the application database.
Regards,
Martin
Martin,
Thanks for the information, we tried this solution(moving the workstation) and were not successful. We have just this week encountered the same problem on a different set of books. This time we are not able to enter or recover, or view any information from the bank, regardless of where you are, the error has even appeared on the General Ledger when we tried to view the bank, as soon as you click on a cell or a view, all cells show “error”. We are not able to reconcile the client’s bank. We had just entered 3 months of data,and two months of payroll and are very concerned about the integrity of this set of books. When all of our books were converted from NV1, there were no errors, and all conversions went smoothly. We have been using the earlier versions of NV2, and had no troubles until we installed the 2.09 and had to decompress our DOS compressed files. We have approx 50 sets of books that we manage, and we are quite concerned that this could happen in any of our other books. We are hoping that you can help us correct the current problem, as well as enlighten us on how this happened in the first place. At this point, we are contemplating creating a new set of books, but then we would not have the history available, which is important to the client, and the lost time involved is wreaking havoc on our budget. Our faith is waning!
Thanks for your helpGo into the application database in single user and review all accounts under NewViews > Account. This will list all accounts in the application database.
I suspect that some of your account names contain one or more of the following characters (as well as the descriptions):
* / # $ [ ] ( ) { } ! “
Remove these characters from the account names and descriptions. Once removed the problems you are encountering will stop.
2.09 is evaluating the account names and descriptions and the characters above are causing the problems.
Regards,
Martin
Martin,
We have gone back to the NV1 version of this set of books and re converted, then we spent the whole weekend re entering the data on NV2. We do not seem to have the error now, so although your solution may have been viable, we were under deadline from the client and had to be creative in order to get the books up to date. This amounted to a huge volume of work for me, in addition to my regular work load. Is there any way this could be prevented from occuring again, is there a script that we could run on all of our other sets of books to see if there is problem just waiting to pop up, and why did we not have the error immediately when we decompressed? Your answers would be very helpful in preventing this from reoccuring.
Thanks,
John MacNeilA script to alert the user about these problems will be added to a service pack of 2.10.0 which is scheduled to be released this week. This script may appear in 2.10.1.
Regards to all,
Martin
Help,
We have been working around this bank view error on a set of books for quite awhile, but have now encountered serious difficulties. We are getting the error on all bank views, and now it is preventing us from opening any other module, AR, AP, etc. We are not able to close the books in the normal manner, and then have difficulty re opening them. We are reluctant to re set up this client’s book, as we did with another set of books, as this client requires all of his historical data. We have reviewed all account names, removed any suspect symbols as you suggested. This problem is very serious, and we need assistance to correct this as soon as possible. You had mentioned a script, is this available, we did not have any trouble until 2.09.
Thanks.
John MacNeil
- You must be logged in to reply to this topic.
