[X]My Assistant

[FrankRuperto]

@Albert

That's a good alternative, unless Greg's IT department has disabled running vb scripts in group policy settings.
What's curious is everything was working until about 3 weeks ago and no mods were made by Greg, so did a Windows, Office, or IT Dept update break it?
Could it be that you are linking to a password-protected backend and the password expired?
Have you run compact/repair on your FE?

The Access error message doesnt seem to relate at all to the problem.
Error 2001 usually occur when Access cannot make sense of part of an embedded SQL statement, or when elements within a Domain Aggregate Function are incorrectly specified.
Perhaps turning on trace and recording it in a log file could reveal, or looking at the Windows and Office Event logs?
You could spend hours trying troubleshoot the problem, only to find out there's nothing you can do about it with the existing setup, so a workaround like Albert's, if allowed, is a good solution.
This post has been edited by FrankRuperto: Nov 1 2019, 04:29 PM

Attached File(s)

 OfficeEvent.PNG ( 46.95K )Number of downloads: 2
 SystemEventLog.PNG ( 114.33K )Number of downloads: 3

 

[FrankRuperto]

@SerranoG

So it occurs to me that since your IT Dept restricts admin privs on your box that they're also auto logging you out of the box, or locking the account which requires a password to unlock, after X amount of inactive time?

If that's true, the task scheduler cannot launch your Access app if no user is logged in.