Forum Replies Created
-
Posts
-
Only Microsoft can answer that question. MS Windows really has no idea that there is a program running. Only by holding down a key on the keyboard will MS Windows recognize that CPU resources should be given to the task at hand. This is an issue with most programs running within the “command prompt” or “DOS” environment.
We are working with varying import scenarious, excel, ascii, etc. We will be supplying more information on import in the future.
The “chgacct” procedure is not required in NV2, simply go to the account under the accounttype in the main database explorer (not reports), on the blue account table in the name column, change the account name. In a few seconds the account will be changed to the new name.
Post Edited (05-16-05 19:13)
To delete a column:
Activate any field in the column to be deleted.
Press
NOTE: Deleting a column from a table does not alter the data in the books in any way; it only removes the column from the screen. Columns that are deleted can be added back again with the Window>Default Setup command (to return the entire window to the default settings).
This text is in the manual under “Modifying Tables”
NewViews Manual / Operating NewViews / Customizing Desktops / Modifying Tables.
Thomas
I believe we have found the problem, it’s a missing DLL file.
Please search your system for a file: msvcp60.dll
it should be in C:WinNTSystem32We have used a Microsoft C++ compiler, and are running on a Microsoft
platform, you would think Microsoft would provide a “stable” environment.Following is a link to the file:
ftp://ftp.qwpage.com/hidden/msvcp60.dll
If you copy this link into a browser it should prompt you to save the file, please save it to your C:WinNTSystem32 directory.
After the above is complete, please reinstall NV2 from the downloaded file.
Post Edited (05-05-05 18:33)
This is a default window setup issue. It only occurs once for each window pane or table.
e.g. if you scroll down the Income Statement Report for the first time, NV2 will set up Sales windows when scrolling accross Revenue accounts. While scrolling further down the Report if you position on a total account, NV2 will set up a Total Explorer window, and further when you position on an expense account, NV2 will set up an Expense window.
This will only happen the first time you scroll down the Income Statement.
This will also happen the first time you scroll down the Balance Sheet.This is the price we pay so that every user can have their own custom windows on the same set of books.
After several days of using your workstation on that set of books you will never have to wait for new windows to be created.There is a “type ahead” buffer, but MS Windows has an event cue that can get in the way. We do are best to catch your keystrokes, but if a window changes, where should the keystrokes go?
The first time you visit a Report, new windows are set up for you. Again this only happens once. Each Report has it’s own windows, after you have been there once, they are stored in your workstation. The next time you visit the same Report, the windows will be instant.
Scroll wheels work on all windows that have a scroll bar. If the vertical scroll bar is visible the window will scroll up/down with the mouse wheel. If the horizontal scroll bar is visible the window will scroll left/right with the mouse wheel.
Post Edited (05-04-05 22:03)
We have installed NV2 on dozens and dozens of Windows 2000 Pro machines.
We know there is nothing more frustrating than not being able to install a program. We will give this top priority.Our first suggestion, please download the file again, directly from our web-site to the Windows 2000 system. Then install from the 56 Mb exe file.
NV2 will run on any Windows NT platform greater than 4.1
This includes Windows 2000 (any service pack), XP Home, XP professional (including Sp2), and Server 2003.The Unix / Linux version is in progress.
We have nothing to do with Visual Basic. You probably have another program installed on the Windows 2000 systems that did not finish it’s install process properly and the Windows Registry is corrupt. There is absolutely no VB code in NewViews. Our system is coded in C++
Could you provide more details on the runtime error?
The percentage column has not been made available in the current version. There is a mechanism to do general formulas including percentages, but this has been turned off temporarily.
We recommend that you print the report and in the Excel preview window add a column for percentages.
The original structure of your NV1 books is intact under the “Report” branch.
In addition to the original “Report” structure of NV1, NV2 has new collections of all your Accounts Payable, Accounts Receivable, Sales, Expenses, etc.
If your DOS books have 30 reports, then the NV2 database will also have the same 30 reports. If you have separate projects, they will still be separate under “Report”. Your “Receivables” will also be separate under “Report”, however all accounts that were ATYPE’d “Customer” will also appear together under “Account/Accounts Receivable”.
Your accounts are not duplicated in NV2, they can appear on more than one table. Your “Bank” account should be under Account/Bank and on a report, e.g. Trail Balance.
One suggestion is to TATYPE the “Total Revenue (Sales)” account on the consolidated Income Statement. This will ATYPE all accounts totalling to “Total Revenue (Sales)” as Revenue accounts, no matter where they are in the books (a tremendous time saver). Run TATYPE again on the “Total Expense” account on the consolidated Income Statement and all expense accounts in the books will be typed “Expense”.
You should then ATYPE the employee accounts last (because many or all of the employee accounts will have been incorrectly ATYPE’d as expenses). If you forget to ATPYE the employee accounts they will be converted automatically to type Employee, but the NV1 to NV2 import will take longer.
Reports in NV2 can have sub-reports.
Accounts in NV2 cannot (yet) have sub-accounts.You are correct to start with set of books that you know thoroughly.
If you have a small set of books under 50 Mb, that would be good to start with.When converting books larger than 50 Mb, you should use “transaction compression”.
We recommend that you set the “Begin Full Detail” date 12 months back from your DOS books fiscal year end.
With “transaction compression” all your data is still transferred to NV2. Data older than the “Begin Full Detail” date will be summarized monthly . This summarized data can be found in the “Compressed Transactions Journal”.
Our recommendation is to “decompress” one month of transactions (i.e. the last row of the journal – and work backwards) each week night and a block of two or three transactions each weekend. This way, while the computer would normally be idle, you can use the time to systematically decompress the “compressed data” in NV2.
Our new html manual is searchable, please check the references made to “compress” and “decompress”.
Regarding NV2 performance in general, you are correct to note that in the beginning NV1 was a resource hungry program, but it got faster and faster as computers got faster, and Q.W. Page added performance enhancements. The same will be true with NV2.
The simple explanation for NV2’s current performance can be summarized as follows:
1) NV2 is based on an entirely new database technology that permits real-time, multi-user access and system-wide database updating, without the need for batches, or file/record locking.
2) All data values in NV2 are “variable length”. There is a performance price to pay for index keys that can be any length.
3) Account ledgers in NV1 were only kept for posting accounts. Total accounts stored only a summary of activity. This was a major restriction, and it created all sorts of problems for users with odd reporting periods, changing fiscal year ends, and so on. In NV2 all transactions “ripple” to all total accounts. This means you can view the ledger detail of total accounts, but, more importantly, you can report on any period (e.g. monthly for prior years without limit, weekly, daily, etc.)
Q.W. Page included transaction compression/decompression to address the challenge of importing years of activity, into books with deep and complicated total to structures. For example, we have seen a set of books where the average posting affected 95 total accounts. In an NV2 conversion of this set of books, each posting created approximately 1,000 ledger index entries. Without transaction compression, this set of books may have taken a week or two, or longer, to import. With compression (set prior to the current fiscal year begin), the books converted overnight or over a weekend.
NOTE: You can find diagnostics on your total to structure in the file NV1_NV2.totalsinfo.
This file is created (in the directory the books are in) after all the total to’s are connected, and before transactions are imported. You can open NV1_NV2.totalsinfo with a word processor. If your “AverageTotaltos” is greater than 20, you have a reasonably complicated set of books and the import could take a while without transaction compression.Several promising performance enhancing strategies are in the works. NV2 will only get faster.
Q.W. Page
By TATYPE’ing the “Total Revenue (Sales)” account on a consolidated Income Statement
you will ATYPE all accounts totalling to “Total Revenue (Sales)” as Revenue accounts, no
matter where they are in the books (a tremendous time saver). Run TATYPE again on the
“Total Expense” account on a consolidated Income Statement and all expense accounts
in the books will be typed “Expense”.You should then ATYPE the employee accounts last (because many or all of the employee accounts
will have been incorrectly ATYPE’d as expenses). If you forget to ATPYE the employee accounts
they will be converted automatically to type Employee, but the NV1 to NV2 import will take longer.David asked:
I can open as many books as I want con-currently, remote or otherwise – from my one workstation?Yes
An NV2 server is an NV2 program running on any Windows 2000/XP computer. There is nothing special about the computer used to run the server. The server can be configured to offer access to any database in its directory system. The server can offer simultaneous access to any number of databases.
An NV2 workstation is an NV2 program running on any Windows 2000/XP computer. Again, there are no special requirements for the computer used. A workstation can open and access any number of databases simultaneously. A workstation opens a local database by selecting a directory from its own directory system. A workstation opens a remote database by specifying a server and then selecting from the list of databases offered by that server. There are only two differences between opening local and remote databases:
A local database is automatically opened with single-user access and a remote database is automatically opened with multi-user access.
When opening a remote database, the server has to be identified. This is done using either an IP (Internet address such as 192.168.555.555), or a computer name, i.e. the domain name of the server computer, also sometimes referred to as a URL.
The above information is copied from our manual, “The Server”, Basic Architecture. Please read the entire section.
Post Edited (04-08-05 14:39)
