Quickbooks Premiere Contractor - help

Hi

Are you running XP??

reject this answer and I will know by your comment you add

fred

Hi

Out of my league

Do this

reject this answer

repost question as "qbw32.exe problem"

up the points given

Your question fell on a holiday and your best bet will be to repost on monday when the big guru's will be sure to see it.

Joseph Moore or TheChas or Sgt Shultz are your best bets though there are many more out there

My humble self thinks QB is ripping you as it may well be a prob with win 2000 32 file

Sorry I could not be of more help

fred

You need to post the log file that was created.
Also need to know the specific type/build of
Windows you're running.

When you say "intermittently" -- does it happen with
the same file, subdirectory, etc.? Does it happen
when you've completed a particular set of actions,
or when certain parts or functions of the program
are open (e.g., multiple transactions at different
stages, or open dialog boxes)? Or is it completely 'at
random'?

The problem could be transient errors in the
memory, the hard drive, etc. -- but installing on a
'new Dell PC' would tend to rule those things out.
What OS was the new Dell running, and did it have all
the 'windows updates' on it at the time you did the
install?

The issue would seem to be either with the
executable, or with the interaction between the
executable and the 'company file' data under the
specific OS you're running. The bad thing is that you
can 'verify and rebuild' just fine, but you can't tell me
precisely WHAT had to be rebuilt, or more precisely
WHAT made the executable disagree with Windows,
and the precise things the executable did that led to
its being shut down.

Continued long note in next post...

This is NOT likely to be something that the QuickBooks
people can solve over the phone, especially if it's a
transient problem, or related to specific config
information on your local machine.

Which leads to a little inherent troubleshooting logic:
the problem is not really in the 'database integrity', it
seems to be in the way that the main QuickBooks
program tries to do something with data it's either
accessing from RAM or trying to write to RAM or the
disk. Which, in turn, might imply that modules being
paged in and out of virtual memory are conflicting
with data writes -- perhaps delayed data writes from
cache. That shouldn't happen, of course, but is the
sort of thing that might require Windows -- not
QuickBooks -- tweaking to avoid.

You might try running a different OS to see if the
problem occurs there too. (This shouldn't
compromise your data integrity, since it just involves
starting the program from within a different
environment). There are ways to set up Windows to
do multiple boot (especially if NT or XP Professional is
your base OS), or you can use one of the third-party
multiboot utilities (which are a bit more complete in
how they isolate the files used by the different
opsystems). "Easy" solution would be to keep using
an OS that doesn't produce crashes...

...and if any version of Windows crashes the same
way, you may get valid additional diagnostic
information from the different error messages...

This question was closed by the author