Solved Avoiding opening the database from OneDrive

but if they did, the front end wouldn't find the BE b/c it wouldn't be in the expected location, so (hopefully), no corruption of the data.

You are correct, the FE would not find the BE. You are also correct that in such a situation, there would be no data corruption. But the down side of it all is that you would not have data corruption because you would be unable to DO anything with the BE if you could not find it to link to it. Can't use what you can't see. Can't bollix up what you can't see - but can't constructively work with it either.
 
Can't bollix up what you can't see - but can't constructively work with it either.
Absolutely - I would hope the company would give me some advance warning before moving the backend.

Then again, I talked them out of it, but I got an E-mail from our Citrix team last Wednesday that they wanted to drop Outlook Classic and go to Outlook web app and had a test environment ready to start testing last Monday and go live week after next.

Out database (and others) probably has 400 calls to Outlook classic that I would have had to modify to SMTP (if I could find the E-mail server location), or DoCmd.SendObject (and figure out WHICH 256-characters I wanted in the E-mail).

(I wouldn't have had to modify 400 locations, but I would have to do something different for that team. (And worse, they only wanted to do it for 6 months and then they were going to Outlook 365 which we run outside of Citrix, so my workaround would no longer be needed after that).

Luckily, I was able to convince them to keep both classic Outlook and Outlook Web.
 

Users who are viewing this thread

Back
Top Bottom