🚀 go-pugleaf

Actually, what Mike said is absolutely correct - and is indicative of damage
within the data file.

"David Ray" <david@timecalc.com> wrote in message
news:3a99c54e.79484878@news.mindspring.com...
> This is the output of a line of debugging code left in by Intuit
> programmers.  Essentially, this is a result of something that shouldn't
> have happened within the program that did.  The programmer judged 
> the likelihood of this event occurring so slight that it wasn't worth writing 
> any kind of recovery method for it.  Obviously, they were wrong.
>
> The V probably stands for "Value", and the -4 is the decimal value of the
> hexadecimal number 0xFFFFFFFC that follows it.  As to what any of it
> "means" I would suggest that only Intuit knows for sure...
>
> "Mike Block - Tax Cut C.P.A." <mblockNO_SPAM@blocktax.com> wrote in
message
> news:3a99a86b.72088577@news.mindspring.com...
> > On Sun, 25 Feb 2001 21:24:56 GMT, Steve <steve@nospam.com> wrote:
> >
> > >the first bad entry in the log reads as follows:
> > >
> > >QBW 15/12/2000 1:14:23
> > >
> > >IDX: 6 ID: 0 RN: 7 SIZE:2880
> > >
> > >V7.0D R3 (M=1352, L=968, C=88, V=-4 (FFFFFFFC))
> > >
> > >Beside the date and time info, what does this mean?
> > >
> > >Thanks,
> > >Steve
> >
> > No idea of the IDX line.
> >
> > Version 7.0 is the version number (probably QB99).
> > R3 is the third interim release in version 7.0.
> > M may be the QB transaction with the error.
> > L is the line in QB where it caused a problem
> > C is the error number listed on my website.
> >
> > C=88 is an Error writing to the QuickBooks file on the
> > QuickBooks file level. Try running rebuild. If problem
> > persists try to free memory and try again.
> >
> > http://blocktax.com/QB%20error%20codes.htm
> > tells how you can often fix files. You reach this
> > from http://www.blocktax.com/ QB Errors.
> >
> > I do not know about V=-4.
> >
> > mike block
> >
> > >JMC wrote:
> > >>
> > >> Do you have all other running programs shut down when you are trying
to
> open
> > >> your file? If not, then close everything and try again.  You can do a
> > >> Ctrl+1,Ctrl+2 to open the Tech Helper.  Click on the Open File and
> scroll
> > >> down and find the QBWIN.LOG and open it.  This makes an entry
everytime
> > >> something goes wrong. On the right side are the entries that are bad,
> if
> > >> any. The second line should say what type of doc it is and to the far
> right
> > >> under doc # is the check number.  You will need to find these
> transactions,
> > >> copy down exactly how they are entered with all info, delete them and
> > >> reenter them with the exact same info. Then try again on your
> > >> File/Utilities/Verify and see what comes up.
> >
> >      Mike Block - Tax Cut CPA
> >  World's #1 QuickBooks Top Tester
> >     FREE  NetLedger accounting
> >   FREE 462p QB books/error codes
> > 100+ QB add-ons http://blocktax.com/
> > QB no-spam news: biz.comp.accounting
> > -----------------------------------
> > Spam bait admin@localhost abuse@localhost
> >  webmaster@localhost postmaster@127.0.0.1
> >  enforcement@sec.gov cyberfraud@nasaa.org
> >
> >
> >
>
>
>
>
>