Hi all,

One of my applications is used by several users, mainly through terminal
sessions. One of the drawbacks with this is (sometimes) the slow
response time. This causes the user to click on buttons again after
initial clicking. E.g. from a swichboard form, if the users clicks a
button to open another form, and this form is not opened as quickly as
expected, the user tries again.

This results in opening the form twice, with all corresponding problems
and errors. The same is when closing the form. Using the "close" event,
data is collected, manipulated and stored. If this button is used twice,
again we may get problems and errors.

So my question is: is there an easy way to prevent this? Of course I can
disable a control/button after initial use, but I do not know if this is
the best solution. In the switchboard form, there are about 10 options.
And disabling all these options separately (and afterward enabling
again) is not my preferred solution.

Can I disable all form events with one command, or postpone/ignore any
input during processing?

Thinks in advance for any suggestions.

Paul

Your problem is not the code as much as it is the way you are using Access
on the Terminal Server. You need to create a folder for each user so that
when he/she logs into the Terminal Server they are directed to their own
folder each one of which has a copy of the Access front-end. Any other
method will eventually cause corruption. possibly irreparably.

If you still have the same problem, start checking the server RAM and the
network for slow or bad NICs. As a last resort, you can change your code to
disable the button after it is clicked once. Then re-enable it after the
code runs.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com


"Paul B" <(E-Mail Removed)> wrote in message
news:4908ab4e$0$27201$(E-Mail Removed)...
> Hi all,
>
> One of my applications is used by several users, mainly through terminal
> sessions. One of the drawbacks with this is (sometimes) the slow response
> time. This causes the user to click on buttons again after initial
> clicking. E.g. from a swichboard form, if the users clicks a button to
> open another form, and this form is not opened as quickly as expected, the
> user tries again.
>
> This results in opening the form twice, with all corresponding problems
> and errors. The same is when closing the form. Using the "close" event,
> data is collected, manipulated and stored. If this button is used twice,
> again we may get problems and errors.
>
> So my question is: is there an easy way to prevent this? Of course I can
> disable a control/button after initial use, but I do not know if this is
> the best solution. In the switchboard form, there are about 10 options.
> And disabling all these options separately (and afterward enabling again)
> is not my preferred solution.
>
> Can I disable all form events with one command, or postpone/ignore any
> input during processing?
>
> Thinks in advance for any suggestions.
>
> Paul