April 11, 2004 at 2:49 am #11315TThibodeauParticipant
Has any one tried to create books for Feb 2004 ?
If you try 29 02 2004 you get an invalid date message.
28 02 2004 does not respond at all.
The only way I found was to create for 2003 and then move it forward one year.
Has someone tried this and had other weird result ?
Could this date cause problems in the future ?
email@example.comApril 11, 2004 at 11:31 am #12512
Interesting problem – and you certainly found a work-a-round ! I tried the same thing – but had no problem with Feb 29, 2004. The year end rule is, and I quote
“The [Current Fiscal Year-End] on the Odds & Ends document is the
date on which the current fiscal year ends. Your fiscal year can
end on the last day of any month. “
So I would suggest you look at your CMOS Computer date. Sounds like it maybe incorrect, but is being “adjusted” by windows to the current date. (when your computer starts, and you can do “Delete” to enter the setup – in this place) – this might cause the problem.
> Has any one tried to create books for Feb 2004? If you try 29 02 2004 you get an invalid date message. 28 02 2004 does not respond at all.
> The only way I found was to create for 2003 and then move it
> forward one year.
> Has someone tried this and had other weird result ?
> Could this date cause problems in the future ?
> Thomas Thibodeau
>April 11, 2004 at 2:22 pm #12513HMahParticipant
Using a Blank set of books (no reports and Odds & Ends with a zero year end date) I also had not problems with setting up books with year end of feb 29, 2004.
Have you gone into your Windows Calander to see if it recognizes Feb 29, 2004?April 11, 2004 at 3:40 pm #12514TThibodeauParticipant
I should have said when using the newviews shell “make books”.
This was reported to me by a client.
I have tried it on 2 computers with the same result.
At the make books date prompt
Feb 28 2004 gives a nvreorg (6) error
Feb 29 2004 it just stays at the prompt.
It seems that ” MAKE BOOKS” from the shell does not see leap years
but nvreorg which actually makes the books does and reports the error.
NVbooks will create the books ok and than you can put in any valid date.
As I said it seems to be only the “MAKE BOOKS” from the shell that has the problem.
Thomas ThibodeauApril 11, 2004 at 3:55 pm #12515
With effort – I am unable to re-create your problem as you describe. Using the Shell, nvReorg, or DOS I had no problems in anyplace with the Feb 29, 2004 date. Again, I would suggest checking the CMOS of your computer(s) for the correct current dates. Perhaps you need to re-install NV program files?
As for the Feb 28, 2004 – read the rules. It will never work. But the fact, that it doesn’t work – indicates the calendar functions are working correctly.
Oh-by-the-way the Shell “Make Books” does require
“Fiscal Year End Date for new books (DDMMYYYY): 29022004”
> I should have said when using the newviews shell “make books”. This was reported to me by a client. I have tried it on 2 computers with the same result.
> At the make books date prompt
> Feb 28 2004 gives a nvreorg (6) error
> Feb 29 2004 it just stays at the prompt.
> It seems that ” MAKE BOOKS” from the shell does not see leap years
> but nvreorg which actually makes the books does and reports the error.April 25, 2004 at 10:14 am #12549BHalpinParticipant
Yes, there is a bug in Make Books.
I remember this coming up in 2000, and it probably came up in 1996 as well.
The solution/work-around is as described in a previous post – make the books with a Feb 28,2003 year end and then roll the fiscal-year-end aread the 1st time you enter the books.
BobApril 25, 2004 at 10:58 am #12550
Not that I want the problem – but regardless of how I “create the books”, I can not seem to reproduce the error.
I wonder what is different about my set of exe files?April 27, 2004 at 9:48 am #12551BHalpinParticipant
– NewViews Shell
– Make Books
– Choose a Template
– Type a directory
– For Fiscal Year End, type: 29022004
Works (fails) for me every time.
BobApril 27, 2004 at 11:25 am #12553
( LOL )
I’d like to believe you – BUT when I do it, it works correctly every time and I can not create the fault !! Perhaps the age of the CMOS ? Or that I am using an Intel Chip on an ASUS Board ?
You can see the results / OE Page at
> – NewViews Shell
> – Make Books
> – Choose a Template
> – Type a directory
> – For Fiscal Year End, type: 29022004
> Works (fails) for me every time.
Post Edited (04-27-04 07:40)April 27, 2004 at 1:08 pm #12555HMahParticipant
Not trying to prolong a minor issue, but neither of the Templates offered with NV is that great.
I suggest creating your own set of books with NO year end date (called whatever) to be used for starting a new client. It may contain generic BS, IS, AR, AP, IR, GST, GJ, etc reports (with mainly all the Total accounts and Total to’s setup) which can be modified quickly to suit the clients needs. If you have a group of Macros or Procedures you install with each books these would be already installed.
I find this works much better than starting from scratch.
Finally you never get the Feb 29th error when changing the year end date in the Odds & Ends of books.
Post Edited (04-27-04 09:16)April 27, 2004 at 1:16 pm #12556
Yes, I would agree, using a custom template – would fit the enduser better
But, Ah – the questions / answers are only about the Year End.
- You must be logged in to reply to this topic.