You must have a really bad network.
The only thing you can do is trap for the error in all your error handling
routines. When you get the first one, you will probably have to tell the
user to try again later and shut the application down.
The only other thing you could do would be to set a timer and use the timer
event to try to relink all your tables and if that fails, tell the user and
start the timer over again.
"eeriksson" wrote:
[Quoted Text] > We have developed an access application with a backend access DB on the
> network. The application contains forms that display a lot of data. The
> problem occurs when the network connection is lost (e.g. when a client goes
> into standy). The forms/queries quite naturally cannot access the data from
> the backend and starts to display the error-message: "object invalid or no
> longer set".
> The problem is that access generates hundreds of these messages for some of
> the forms. Is there a workaround?
> 1. Maybe there is some way to make access wait for the connection to be
> available instead of throwing errors?
> 2. Otherwise, can this error message be supressed?
> 3. If that is not possible, can the user somehow close one or all forms (to
> stop the messages coming) without exiting the application.
>
> Any help is appreciated!
>
> /Erik
|