AOB
Registered User.
- Local time
- Today, 03:14
- Joined
- Sep 26, 2012
- Messages
- 637
Hi guys,
I have a 'standard' Access application in place - split FE/BE, BE on a shared network drive, individual FE's on each user's local machine. Has been operational for several months with no real issues (i.e. nothing I haven't been able to isolate in code and correct to prevent future recurrence)
This morning, I checked the error log (as I do most days, just to see if anything unusual has cropped up) and found one of my users hit an Error 3239 ("Too many active users") when opening the FE
(The error handler / logger tells me the sub/function and module where the error occurred, and on this occasion it was the function to relink the tables using the drive mapping specific to the local machine. This is only called once, at startup, to reduce latency in the data connections)
I've never seen this error occur before, and I doubt very much it is actually due to there being too many active users (at the time she tried to open the FE, there would have been 9 other people connected; I have, in the past, seen up to 14 or 15 people 'active' at any given time, in the sense that they had the application open, and it has never been an issue?)
Is this something I should worry about (and how would I go about handling such a scenario should it arise again) or could this just be a freak occurrence due to network issues (out of my control anyway) or a rare concurrency event that is unlikely to arise very often?
Thanks in advance!
Al
I have a 'standard' Access application in place - split FE/BE, BE on a shared network drive, individual FE's on each user's local machine. Has been operational for several months with no real issues (i.e. nothing I haven't been able to isolate in code and correct to prevent future recurrence)
This morning, I checked the error log (as I do most days, just to see if anything unusual has cropped up) and found one of my users hit an Error 3239 ("Too many active users") when opening the FE
(The error handler / logger tells me the sub/function and module where the error occurred, and on this occasion it was the function to relink the tables using the drive mapping specific to the local machine. This is only called once, at startup, to reduce latency in the data connections)
I've never seen this error occur before, and I doubt very much it is actually due to there being too many active users (at the time she tried to open the FE, there would have been 9 other people connected; I have, in the past, seen up to 14 or 15 people 'active' at any given time, in the sense that they had the application open, and it has never been an issue?)
Is this something I should worry about (and how would I go about handling such a scenario should it arise again) or could this just be a freak occurrence due to network issues (out of my control anyway) or a rare concurrency event that is unlikely to arise very often?
Thanks in advance!
Al