Univeral Error Handling?

[Matter]

Hi All,

I've been getting the classic "Network Access Interrupted" error on our FE/BE database here on site. The problem is most definitely wifi cutting in and out, as the end users are all using laptops out-doors at varying distance from access points.

The real annoyance is that the error pops up once for every form open, so a momentary lapse in network access can pop up 5-10 text bubbles and that annoying beep.

What I'm hoping to do is code an error handling that the notice is replaced with a custom message that only pops up once and suppresses having multiple dialogue boxes. If possible I would also like it to try to reconnect to the backend without opening and re-closing, as this is a daily occurrence. Can you point me to resources to help me achieve this goal? Thank you!

Cheers,
Matt

 

[DCrake]

For a start I would seriously recommend not using wifi with split databases as any momentary loss in connection will lead to corruption in your data.

Imagine that Access is performing a write to the table and the connection drops half way through, the entire write will not be completed and as such the record is fragmented.

I am sure there are others on this site that share the same feelings as me.

 

[Galaxiom]

Change to running Access via Terminal Services.

This runs Access front ends on the server and provides a view to the remote clients, responding to keystrokes sent to the server from the cleints.

 

[Matter]

Change to running Access via Terminal Services.

This runs Access front ends on the server and provides a view to the remote clients, responding to keystrokes sent to the server from the cleints.

If I understand what you are saying correctly, this is akin to running it from a remote-desktop session. My experience with remote-desktop is that it is even more bandwidth intensive than my current frontend-backend system. Perhaps it is better still to run it as an intranet website to a postgreSQL backend?

Do you have links to more information about this? I am probably misunderstanding what terminal services entails.

 

[Galaxiom]

Terminal services and Remote Desktop are the same thing. Microsoft changed the name.

Bandwidth intensive but with the advantage of fault tolerance. Losing connection just loses the view rather than half the code execution.

A well designed web application is definitely a better solution but that means rewriting it.

 

[Banana]

FWIW, one can use Access across WAN against a server-based RDBMS such as PostgreSQL and that requires less rewriting than a web application and would probably perform better because there's less network traffic via ODBC connection than via HTML + text. It works because Access talks to the local ODBC driver and it's the ODBC driver that handles the connection across the internet.

Terminal Services has been excellent solution as well, just a horse of different color.

 

[Galaxiom]

Yes but the original problem is with interrupted connections. The html solution is more tolerant because the server doesn't query the database until it has gathered a complete set of instructions from the client.

 

[Banana]

No argument there. I may have misread the OP but I was understanding that he was using Access backend across a wireless connection, which as DCrake rightly pointed out was a no-no. (Same applies for WAN connectivity) At least with ODBC connections, it works better and is more tolerant compared to that scenario of using Access backend.