Pause and Continue

[seaport]

I wrote a progrom in Access 2000 to generate some statistics (saved in a table) for each divisions (total 37 divisions). It takes about 4 minutes to generate data for one division. So the total process takes about 2 hours. Certainly, the Access database becomes "no responding" during the process.

How I can make the program "responding" during the process? Further, how can I pause the program (click the button and the program pause after completing one division) and continue the program?

Thanks in advance.

Seaport

 

[TheAceMan1]

How are seaport . . . .

I have designed several databases with runtimes greater than 7hrs, and have never had the problem you describe.

I could be wrong, but, maybe you need and APC?

I'm highly interested in what other Guru's would have to say here . . . . . since you have just made me a little nervous! :-(

TheAceMan

 

[seaport]

TheAceMan,

Sorry if I confused you. My database works OK and generates correct results after two hours. During the process, if I click the Windows task bar for this database, the screen does not refresh and, if I check Windows Task Manager, it shows that that database is not responding. I know my database working fine and will "respond" after the process is done. What I like to have is a form showing the progress of the processing job and let me to pause this process if necessory.

However, if the database becomes "no responding" during the process, I can never get to that form to see the progress and pause the process.

Seaport

 

[Edski]

So put a progress metre on your form. There's plenty of tips here on that. Just do a search.

Yeah, the Windows Taskbar isn't too clever in that regards. I get that all the time (Not responding) but I just ignore it - coz I know it's still running ok.
Cheers.

 

[TheAceMan1]

OK seaport . . . . .

I checked my documentation and your right. One of the databases I described had the same problem and in a bad way. During runtime the DB would build huge amounts of data in memory. To the point where you could call it a Resource Guzzler. Users were given specific instructions to kill all other running programs, including those deemed unnecessary running in the background. It was only then that the DB ran unfeathered. In one specific case, it also had to be run Exclusively.

As for pausing runtime, I've never had to do it, but I believe you can program in the detection of a key combination and go from there. Researching this at this time.

As for the ProgressBar . . . see . . . thread702-793084





TheAceMan