Runing 2 things at the same time

  • Thread starter Benjamins via AccessMonster.com
  • Start date
B

Benjamins via AccessMonster.com

Hi,

I using Access 2003

I have a module. The module will open a form when it was executed and will
close the form once finishes.

The from has a label to show the user the system is still processing by using
the form timer. The form works fine working on itself.

Once i use the module to run the code, the form loaded but does not show
anything and close once finished

Below is the example of Code

Module:
Public function StartModule()
Docmd.OpenFrom "ProcessBar"
'Code that is need for the module
...
...
...
Docmd.Close acFrom "ProcessBar"
End Function

How do i make the form work.
 
T

Tom van Stiphout

On Thu, 25 Feb 2010 03:25:09 GMT, "Benjamins via AccessMonster.com"

Perhaps you need to place a strategic "DoEvents" call so the screen
has time to update itself.

-Tom.
Microsoft Access MVP
 
B

Benjamins via AccessMonster.com

Never Mind... Found a way to handle this issue...Thanks For the help.
how do i use the DoEvents
Perhaps you need to place a strategic "DoEvents" call so the screen
has time to update itself.
[quoted text clipped - 7 lines]
 
J

Jeff Boyce

Consider posting the solution you found ...

Someone else in the future may be looking for exactly the same solution ...

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

Benjamins via AccessMonster.com said:
Never Mind... Found a way to handle this issue...Thanks For the help.
how do i use the DoEvents
Perhaps you need to place a strategic "DoEvents" call so the screen
has time to update itself.
[quoted text clipped - 7 lines]
How do i make the form work.
 
B

Benjamins via AccessMonster.com

Although it does help to solve the issue, i don't really find it useful...

- Seperate the code into 2 database ( 1st is the Running bar, the other is
the operation.)

- Once the running bar starts, it will call the operation database in hidden
mode which will quit upon finished.

- The running bar will check whether the operation database has quit. if so
it will stop the bar.

Jeff said:
Consider posting the solution you found ...

Someone else in the future may be looking for exactly the same solution ...

Regards

Jeff Boyce
Microsoft Access MVP
Never Mind... Found a way to handle this issue...Thanks For the help.
[quoted text clipped - 5 lines]
 
B

Benjamins via AccessMonster.com

Although it does help to solve the issue, i don't really find it friendly...

- Seperate the code into 2 database ( 1st is the Running bar, the other is
the operation.)

- Once the running bar starts, it will call the operation database in hidden
mode which will quit upon finished.

- The running bar will check whether the operation database has quit. if so
it will stop the bar.

Jeff said:
Consider posting the solution you found ...

Someone else in the future may be looking for exactly the same solution ...

Regards

Jeff Boyce
Microsoft Access MVP
Never Mind... Found a way to handle this issue...Thanks For the help.
[quoted text clipped - 5 lines]
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top