I have been running it for months, but then I went on a trip( not vacation!) and came back and it wasn't working, so I went about a month without running it.  When I finally got it working yesterday I had to get up and walk away it took so long- at least 15 maybe 20.  So I think it's normal- just let it run.  After it has processed a whole (practically) month's worth of transactions, it won't take so long if you do it daily or at least a couple of times a week.
Of course I don't know what happens to it if you stop in the middle of running it.

Well I have let it stay on refresh for the last 5 hrs and it never stops. All the numbers look the same as they all flash. I have no clue what is up!
 
John

no it doesn't hurt it to interrupt the process. the next time you go back in, it will pick up and perform the refresh.
 
all the items you have posted, thru GL-O are being tagged, so it has to go thru your gl files so it can come up with the numbers. they then store this info in seperate data files.
therefore when you have new daily transactions, the Bus. Stat. knows what records it has already used for calculations.
 
it's possible that you might have some transactions that are dated in the future. that will cause a long delay as well.
 
but the 1st time it runs, and you've been using dba/evo for a long time, yes it will take a while the 1st time.

Can anyone help me figure out where to look for differences in the Business Status Report and GL balances?  I have two accounts that do not equal the GL balances.  
 
My first thought was the check register balance - as we do not balance ALL bank accounts via reconcile check register.  But, it's not those balances either!
 
Thanks.
 

I could Use those
 
J Dub

will there be a fix to make the numbers stop flashing??

mmmm, sounds like some settings on your Pervasive might need to be adjusted.  
btrieve error 3006 is the MicroKernal router detected an invalid session..... i know, another cryptic definition,
 
but since the Business status is processing a lot of data, and probably taking it's own sweet time about it, some of the Memory buffers on the server might be getting overloaded.
 
on the server, configuration, set the Communication Buffer size, Read Buffer size to a higher value.
 
also, limit Network protocols to TCP/IP only,
maybe utilize the Auto-Reconnect function,  
and/ or increas the number of remote sessions.
 
of course i'm saying all this without regard to what version of Pervasive you are on. but those are, in a nutshell, probably, likely, some things to help resolve this specific issue
 
after you make the setting changes on the server, you do have to kick everyone out of EVO and Restart the Pervasive services.