Forum Replies Created
-
Posts
-
On the new server:
– Install NV2
– Copy the ‘books’ database from the original machine onto the server drive (location not important – put it somewhere that makes sense to you.)
– Run the NV2 Server program (Start > All Programs > NewViews 2.0 > Server)
– Click Ok to the “Create a server” prompt.
– On the top (buff coloured) server window, insert a line and click on “File”
– [F3] to pop up the “Select a Database” window and navigate to the database file you copied from the original machine. Click “Select”.
– Back on the server line, press [F5] to insure the line is recorded.
– Determine the machine name and I.P. number. Right-click on “My Computer”, choose “Properties”, then click the “Computer Name” tab. Note the “Full Computer Name”. For the I.P. number: Start > Run > Command. In the console window, type: ipconfig [Enter]. Note the IP Address. Type exit [Enter].
On the (original) workstation:
– Insure you can connect to the server machine:
Start > Run > Command. In the console window, type: ping
[Enter]. (Substitute the name you noted in the previous step.) (Don’t put <> around the name.) You *SHOULD* see “reply from ..” repeat several times. If not then try: ping
[Enter] (Substitute the IP number you noted in the previous step.) (Don’t put <> around the number.) You *SHOULD* see “reply from ..” repeat several times. If neither of these worked, then you have a network problem that must be resolved before NV2 will work.
– Run NV2.
– On the line you originally opened the books with, in the “Server” field, type in the computer name or IP number (whichever worked. If both worked, you can use either.)
– Click on the “File” field and press [F3]. You *should* get a little select box showing the database filename you set in the server. Click Select.
– Change the state from Closed to Open as usual.
Licensing Issues:
Right now the server is not ‘licenced’, so you will likely get some sort of notification to that effect (without testing it, I can’t recall exactly when.) So, you will need to contact Q.W.Page and purchase a license for the server. You can do this over the phone (have your Visa or MasterCard ready.) (Call when you are in front of the server machine with NV2 already installed.)
Bob
Hi.
I’m not sure what you mean by “subcontractor payroll”.
I must be missing something – I would think that a subcontractor who is an incorporated company would maintain their own payroll to pay their employees, and invoice you like any other supplier.
If the workers are, in fact, paid from your payroll, then NV2 payroll allows you to setup any number of earnings & deductions you need.
What needs are not accommodated?
Bob Halpin
Retroactive pay increases should be taxed in the same way as a bonus. Therefore the account should be setup in the same way as a bonus.
But, most employees and employer’s object to the high tax rate applied to the amount, so they don’t do it. But, the high tax is correct. The employee will end up paying it in the long-run anyway – either through a lower refund or a higher tax payable when they file their return.
Here’s a link to T4001, Employers’ Guide – Payroll Deductions and Remittances:
http://www.cra-arc.gc.ca/E/pub/tg/t4001/README.html
See page 23 – “Bonuses and retroactive pay increases”. Just by the title you can see that they are treated identically for tax purposes.
Bob
This info is on the DOS payroll update section at qwpage.com, but applies to NV2 as well:
(Except from T4127, Payroll Deductions for Computer Programs, 85 Edition)The Minister proposed a new non-refundable tax credit amount of $2,000 in respect of children under 18 years of age at the end of 2007. If a child born in 1990 or later resides with both parents throughout the year, either parent (but not both) may claim a $2,000 personal amount. Any unused portion can be transferred to that parent’s spouse or common-law partner. If the child does not reside with both parents throughout the year, the parent who is entitled to claim the amount for an eligible dependant can claim the amount for child tax credit.
The Minister proposed increasing the spouse or common-law partner amount and the amount for an eligible dependant from a maximum of $7,581 to a maximum of $8,929. The amount will be reduced by the partner or eligible dependant’s net income for 2007.
A revised Personal Tax Credits Return TD1 will be available for July 2007.
Bottom line: Employees should fill out a new (Jul 07) Federal TD1 and you use the revised claim amount they supply in their payroll setup (Deduction Information, Federal window.). The $2,000 is not entered separately anywhere in the payroll.Bob
Yup.
I tried the same thing – Begin 000 00,00 and End Dec 31,07, Type Budget. WHen you enter an amount it all get’s lumped into the last month of ’07.
The fun starts if you then change the Begin date to January 1,07 and then edit the 1,200.00 to 0.00. You end up with Jan – Nov all set to -100.00, and Dec set to 1,100.00
It’s perfectly logical that it would do this (evenly apply the -1,200.00 to each month of the year), but you can tie yourself up in knots unless you know how to use the History view to clean things up.
Bob
Here is what is going on.
Let’s say you are at the report level, with the type set to Budget, and a period of more then one month.
When you edit the amount shown on the report, the difference between the original amount and the amount you entered is divided by the number of months in the period, then each month is increased/decreased by the monthly amount. Simple enough. And in the case where you have a period of one year set and the original amount was zero, you end up with the 12 monthly budget amounts all set to 1/12th of the amount you entered.
But, you can end up in a dog-fight with the budget amounts if you inadvertanly edit a budget amount when the period is not set to a complete year. If, say it was set to 10 months, then any change you make will be equally applied over the 10 months, and the other two months will remain unchanged. Zeroing out the years budget amounts can be tricky too if the months are not all equal to start with. In that case whatever change you make is equally applied to the 12 months and you won’t end up with zeros in every month.
As was suggested above, don’t fight this at the report level (unless you like frustration.) Just expand into the account and go to the History view. In the 1st column set the Type to B and the Rep to M. Now you can zero out the months or set different amounts for each month without any problem.
Bob
> The only way I have found that works is to define
> my column by month and then insert the monthly budget
> amount and then redefine the column for the next month.If you work on the Multiple-Period Analysis or Custom Analysis with the columns set to the 12 months of the year, then you can work across a row setting the twelve months without the bother of changig the column dates from one month to the next.
If you are entering budgets on multiple reports, click on NewViews > Report so that you get the ‘brown’ table of reports in the right-pane. Activate one report and in the account (blue) window below, set the analysis to the twelve months you are budgeting. Now, when you click from one report to the next in the top pane, the bottom pane will alway’s have the same analysis settings. (As is opposed to clicking an individual report in the left pane where the setup for each report is independant of the others.)
Right off the bat – do not, I repeat, do not rely on diskettes for backups.
Over the years QW Support has had to rescue countless users who backed up on diskettes but then found them unusable when the need came to do a restore. (It was actually one of the most interesting parts of the job.)
Here is why:
Under Windows, a program writing to a diskette has absolutely no way of verifying that the data it asked to be written is in fact on the diskette and readable. The “write verify” option that DOS programs relied on before Windows is totally unreliable – and here is an example: I’ve copied a file to a diskette and then taken the diskette to another machine and tried to copy it from the diskette – and I get a read error on the diskette. In fact, I get a read error no matter what machine I try the diskette in. I go back to the original machine and do the copy again; no problem reported. If I immediately use the command-line command COMP to compare the original file to the copy on the diskette it reports the files are identical – BUT – the diskette light never comes on during the compare. This tells me that COMP is being fooled by Windows who has cached a copy of the original file in memory during the copy, and COMP is being fed the cached copy to compare to – not the copy on the diskette. If I pop the diskette out and then back in and do the COMP again I get a read error because there is in fact a bad sector on the diskette, and popping the diskette out caused Windows to discard the cached copy and actually do a proper read of the diskette to perform the compare.
That was long-winded – but it’s really important stuff.
The bottom line is this: DO NOT TRUST DISKETTES FOR BACKUPS. At QW, we became pretty good at predicting that with each additional diskette in a backup set the chances of being able to succesfully restore from those disks went down by 10%. So, if you backup took 10 diskettes, our prediction would be that your chance of restoring from them is zero – and we were usually right.
Another example: I recently bought a 1 Gb USB drive to replace my trusty old 256 Mb one. Guess what? I got stung twice by copying data to the drive and going to a client’s office and finding the data on the drive was corrupted. I returned the drive and got a replacement and it works fine. Correction: (and important distinction) It has not failed YET.
So, what do you trust your backups to? The answer is nothing – you can’t trust any media to be readable when disaster strikes. All you can do is use multiple backup methods/media (CD, USB drive, tape, etc.) to make sure you are covered. So, backup onto USB drives (plural) – they are cheap and pretty reliable. Also, do backups on CD. Backup to another machine in the office. Mix and match these methods and you reduce your chances of disaster to near zero.
Now, with that diatribe over I’ll address your reply above. If you stop using diskettes for backup and move to a method with ‘modern’ speed and capacities, it won’t matter how big your books get, and the need to start fresh books every year is gone.Bob
Do you mean that the name of the company is not seen?
If so, do this:
– Work your way down to Object > NewViews > Account (clicking [+] signs where necessary.
– Once you have clicked on Account click on the Window list button at the top-left of the right-hand pane. Click on “Company Address Information”.
– Click on the line that say’s “Company Name” (line 1) and enter the name of the company
When you press [Enter] the explorer at the left will jump around a bit but then Object will be replaced with the name you entered.
Bob
In my NewViews career I have run across a small minority of (DOS NewViews) users that do this – and I have never really understood why. When I ask, they usually don’t know either – they are just doing what someone did before them, and it’s been going on for years and years. (And, quite often they don’t know about making a template of their existing books and creating a new set based on the template. That makes the job a *lot* easier.)
Some believe you have to do this, but the only reason this could be true is if your books grow to 512 megabytes in a year (which is pretty rare.) Others don’t like to see all the old transactions in their accounts – and that is a subjective reason which I can’t argue with. Then there are those who were never shown how to simply set the Begin and End dates on their Income Statement (and related reports) to the new year. They truly believed that you had to start a new set of books every year and were simply amazed to find out that you didn’t. (The same thing applies to ‘closing the books’ – but that’s another discussion.)
So, now to NV2.
Yes, it would be possible to copy the database files to a new directory and then delete all of the journal entries. Here are the pros and cons:
– Pro: It would be easy. While I haven’t tried it, it would (should) be simple to click on the “root” Journal and then block all journal entries and do Block Delete. This would destroy EVERY posting in the books in one operation (And it would be a lot simpler than trying to do it in NV1 by the way, where you would have to go to possibly hundreds of places to delete transactions.)
– Con: The audit trail. The audit trail would contain a record of all the deletions on top of all the create operations that were there to start with. There is (presently) no way to ‘clean out’ the audit trail so you would be stuck with all those entries.
– Con: Time required. This is totally dependant on the speed of your system, the depth of your total-tos, the number of transactions, etc. Suffice to say the mass delete could take a long time.
I’m willing to bet that QW will at some point release a utility for NV2 to make ‘cloning’ a set of books a routine matter – but it is not here today.
I’m curious: What is your reason for starting a new set each year?
Bob
Ok, this is now straightforward (sort of.)
What’s going on here is the NewViews program files (the ‘core’ NewViews, if you will) have a serial number embedded in them. But, it sounds like a productivity disk you installed is not serialized. Which PD Disk? That depends on what procedure you tried to run when you got the error message.
Background: The NV1 procedure library that comes with NewViews is not serialized. All Productivity Disk and Payroll libraries are though. And, when you run a procedure from one of these it will give you an error if the library’s serial number doesn’t match your NewViews program serial number. Also, an error message is displayed if the library disk you installed was not serialized – which sounds like the error you are getting.
In the long run you should do what the Error/Help say’s – contact Q.W.Page. They will sort you out in short order.
Bob
This is not a Windows 98 issue.
It may be that you installed a (really) old 1.41 update version that was unserialized. These disks were intended to be installed ‘over top’ of a 1.40 version, and would ‘assume’ the existing serial number.
You will need to do one of:
– Locate your latest (1.41b) diskettes and install them
– Copy the NV program files from the old machine to the new one
(Unlikely if the box bit the dust)
– Locate a backup of the NV program directory from the old box and
copy it into the new machine’s NV directory
(Again unlikely – most people didn’t backup the program directory)
– Purchase replacement program disks from Q.W.PageBob
Henry’s got the solution right. Here are the details of what you’ve run into.
Every account stores a number to be assigned to the next transaction to be added to the account’s ledger.
This “next transaction number” starts at zero when the account is created.
Every time a ledger item is added to the account (either directly by adding an item to that ledger, or by posting an item from another account) the counter is incremented by one and the transaction is ‘stamped’ with the new number.
The number maxes out at 64k – once the next transaction number reaches that point then no further transactions can be added to the account.
The next transaction number is *NOT* decremented when you delete or purge transactions.
So, why would you get that error if there are only 70 or 8,000 ledger items in it? It’s because over the life of that account 64k items have been added – whether they are still there or not does not matter. Look at it this way: Say you you create a new account. Then you insert a ledger item and then delete it. Repeat the insert and delete 64k times and you would get the ledger item limit exceeded error even though the account is empty.
Fixing it, as Henry suggested, it straightforward. Backup the books and then run Reorganize Books. In this process all accounts are newly created (with the next transaction number at zero) and it will only be incremented as many times as there are ledger items added to the account when the books are rebuilt.
The end result will be you account’s next transaction number will be reset to whatever count of items are currently in the account (70 or 8,000) and you can continue posting to/from the account.
Bob Halpin
http://www.softrite.ca> I think I’ll have to give up.
I (and many others,) know that feeling.
> If my printer is returning error codes, and it very well could be because my NewViews program is from 1993 and my HP2200 is probably only 6 years old, I’m in for trouble.
The relative age of the software and the printer really have no bearing. I’m using an HP 3330 and al is *usually* well. One in a while (like every couple of months) I’ll boot-up and cannot print. “Clobbering” the system with net use lpt1 /delete and then net use lpt1 \computerprinter /persistent:yes sets it straight again. Why? Who knows – but I could grow old and die before I ever figured it out.
> Hasn’t everybody els had problems lining up their print pages?
This is a separate problem and, thankfully, much easier to fix. But let’s make sure we’re on the same page (pun intended) here. Net use and all it’s ‘niceties’ is strickly concerned with getting output to the printer. Once that is happening then HOW the putput looks (ie: lining up print pages) is a new issue – one that you would face with any printer hookup (even under plain old DOS.)
So, if you’re having problems with ‘lining up pages’ then give some specifics and I/we will help.
> I’ve also noticed that New Views is “freezing” at least once a day. This occurs when I have left the NV DOS window open and come back to it after doing other things in windows 2007.
What’s going on here is the ‘chunk’ of memory NV is running in has likely been swapped out to disk to make room for the memory required by active programs. When you switch back to NV Windows has to swap something else out, then read in the memory for the NV session from disk. The less memory you have, the more this will happen. Conversly, the more memory you have, the less this will happen. If you system is 512 Mb, then an easy fix is to pop in another 512 Mb. (Or, go from 1 Gb up to 1.5 or 2.)
> I just think Microsoft is trying to push everyone out of DOS.
Yup, and you can hear the screams all over the Internet from users of all sorts of DOS programs.
> I tried someone’s suggestion to employ DOS2USB.com’s program.
I have managed to avoid using this program – and will continue to based on your experience, and the complaints I see on the Internet from others that have tried it. There are some who love it – and that’s great for them. But to me it seems like a bit of a waste to buy and install a program to allow you to print to a printer (HP 2200) that is perfectly capable of working with a DOS program already. It adds another layer of complexity with the result that if something doesn;t work you now have another thing to fiddle with.
> Now I can’t even print. I don’t know what happened to the DOS2USB program.
> It no longer shows up.Google DOS2USB and you will probably find others who have experienced similar problems and if you’re lucky a solution is there as well.
Good luck!
Bob Halpin
http://www.softrite.ca
