CPGDeveloper
Board Regular
- Joined
- Oct 8, 2008
- Messages
- 190
So I have come across a very peculiar situation --
I've developed an Access 2016 DB for my team -- there are about 10 end users -- each of them have their own executable on their respective desktops. The DB is Split -- the executable is the front end, and there is a separate MS Access back end.
For one particular user -- his database will suddenly, without warning, shut down. There is no error message and no warning. It's as if a ghost suddenly executes 'DoCmd.Quit'
None of the other users are having this issue. Everyone essentially has the same system -- same hardware, same operating system, same version of access. I've replaced his executable multiple times -- thinking that perhaps it became corrupted somehow. But it doesn't seem to make a difference. I'm at a loss.
By chance, has anyone experienced anything like this? Perhaps there is a setting or requirement I'm missing? Any help would be much appreciated. Thanks in advance.
I've developed an Access 2016 DB for my team -- there are about 10 end users -- each of them have their own executable on their respective desktops. The DB is Split -- the executable is the front end, and there is a separate MS Access back end.
For one particular user -- his database will suddenly, without warning, shut down. There is no error message and no warning. It's as if a ghost suddenly executes 'DoCmd.Quit'
None of the other users are having this issue. Everyone essentially has the same system -- same hardware, same operating system, same version of access. I've replaced his executable multiple times -- thinking that perhaps it became corrupted somehow. But it doesn't seem to make a difference. I'm at a loss.
By chance, has anyone experienced anything like this? Perhaps there is a setting or requirement I'm missing? Any help would be much appreciated. Thanks in advance.