I’m backing up my BE from within Access; although the filesize is relatively modest (15Mb) for this day and age it can take 3 or 4 minutes for the backup to be completed. There’s nothing I can do about that, it’s a network issue beyond my control. My problem is that Access is semi-suspended whilst the backup takes place; I say semi-suspended because if the user goes into another windows app e.g. explorer, word etc, and then back into access, the screen will go blank and it will appear as though access has hung. It hasn’t of course, it’s just waiting for the backup to be compoleted.
Hiding the windows file copy dialog has no effect on the problem, just means there’s nothing to view. Ditto putting up a little popup to say ‘backing up, please wait’ etc.
Ideally I’d like to trigger the backup and immediately return control to the user with the file copy taking place entirely outside of Access. I’ve tried triggering a batch file instead of an API call, but this too makes no difference, the problem remains. Alternatively I’d settle for ‘locking’ the user into access until the code has finished. Does anyone have a solution for either of these, or a better suggestion. Unfortunately I can’t take the easy and obvious route (network backup), that would require a degree of coordination well beyond this organisation!