We've tried running COM access communicating through the server (both on the same machine and separate machines) rather than locally, unfortunately it is *way* too slow for our application. I guess that the network overheads are substantial, particularly given that our requests are quite small and numerous.
Unfortunately the crashing tends to occur only at peak times so we'd have to massively inconvenience our (large number of) users in terms of slow speeds in order to see whether the crash still occurred in this scenario.
Hi John - thanks for the advice.
We've tried running COM access communicating through the server (both on the same machine and separate machines) rather than locally, unfortunately it is *way* too slow for our application. I guess that the network overheads are substantial, particularly given that our requests are quite small and numerous.
Unfortunately the crashing tends to occur only at peak times so we'd have to massively inconvenience our (large number of) users in terms of slow speeds in order to see whether the crash still occurred in this scenario.
I'll look up Bob though - thanks again.