ChrisO
Registered User.
- Local time
- Tomorrow, 03:02
- Joined
- Apr 30, 2003
- Messages
- 3,202
Indivisible process animation.
With indivisible processes, trying to display a progress bar or meter is difficult. Unless we can ‘hook into’ the indivisible process we have no idea of the current step in the process. Without the current step, progress is not known. It therefore becomes a problem to display progress within indivisible processes. In a sense, apart from the indivisible process, Access becomes ‘dead in the water’.
However, we may like to display some animation of a continuation of an Access process.
Indivisible processes in an instance of Access will prevent that instance of Access from updating itself, for example, the Timer event will not fire.
But two concurrent running instances of Access will allow an animation of a continuation of an Access process.
This A2003 demo uses two independently running instances of Access to show a continuation of an indivisible Access process. It is not a progress indicator but a continuation indicator.
In essence, the Access application running the indivisible processes starts another instance of Access to show the continuation. That other instance of Access uses its events to show the animation.
It may sound simple but I do not recommend it.
In my view it adds too much complexity simply to achieve what might be called ‘lipstick on a pig’.
This A2003 demo comes in two parts and both need to be downloaded to the same directory.
Pig.mdb is the test bed and is the database to run for testing.
LipstickOnAPig.mdb is the lipstick database but it can be run separately.
(If you run it separately you should get a continuous translucent popup which will need to be closed twice.)
Please make of it what you may.
Regards,
Chris.
With indivisible processes, trying to display a progress bar or meter is difficult. Unless we can ‘hook into’ the indivisible process we have no idea of the current step in the process. Without the current step, progress is not known. It therefore becomes a problem to display progress within indivisible processes. In a sense, apart from the indivisible process, Access becomes ‘dead in the water’.
However, we may like to display some animation of a continuation of an Access process.
Indivisible processes in an instance of Access will prevent that instance of Access from updating itself, for example, the Timer event will not fire.
But two concurrent running instances of Access will allow an animation of a continuation of an Access process.
This A2003 demo uses two independently running instances of Access to show a continuation of an indivisible Access process. It is not a progress indicator but a continuation indicator.
In essence, the Access application running the indivisible processes starts another instance of Access to show the continuation. That other instance of Access uses its events to show the animation.
It may sound simple but I do not recommend it.
In my view it adds too much complexity simply to achieve what might be called ‘lipstick on a pig’.
This A2003 demo comes in two parts and both need to be downloaded to the same directory.
Pig.mdb is the test bed and is the database to run for testing.
LipstickOnAPig.mdb is the lipstick database but it can be run separately.
(If you run it separately you should get a continuous translucent popup which will need to be closed twice.)
Please make of it what you may.
Regards,
Chris.
