Recent content by GPGeorge

Whether this diagram represents an appropriate design depends on how you need to track the data. Are you ONLY interested in an employee's Position, Shift, Assignment and Training TODAY? Do you need to keep track of an employee's current AND prior Positions, Shifts, Assignments and Training Do...

Irony is the art of expressing outrage when others mirror one's actions.

That's true. I was conflating this thread with another one where the OP was talking about customers.

This is an extremely important point. You have roughly 3 years to identify, develop and deploy the replacement for so-called Classic Outlook. Probably less than that as you can't count on your customers all waiting until the last possible moment to adopt the New Outlook just to support your...

Hm. That interpretation hadn't occurred to me. It's equally plausible, perhaps even more so than my own initial reaction.

No, New Outlook does not support COM automation. You can not send email from Access to New Outlook because of that. There are alternatives, including reinstalling what they now refer to as Classic Outlook. You can explore other options here: and here

"The forum can do anything they want with it.". That includes deleting them. 😉 Jon, as the site owner, has good an sufficient reasons for his management decisions. Far be it from me, at least, to question those motives or decisions.

That depends on what you mean by "running across it in Access". Importing data from a Web API is one place where you'll find it, a lot. And so on. Where to find VBA tools for JSON: https://github.com/VBA-tools/VBA-JSON

As long as both the Office version and the Access runtime are the same -- both click-to-run or both Windows Installer -- they are compatible.

Point 1. No, not all M365 plans include Access, though most do. You should be able to install the Access runtime in most cases. However, you're comments about compatibility are appropriate, I think. It depends on what versions your customers have and how they were installed

We're not talking about composite keys, we're talking about a unique index on two fields. And When a unique index is created for the fields in this table, the database engine does all of the work described in your second paragraph, except for converting the database engine's error message to a...

Seriously? "....let the "interested" beginners do the Debug session in their own time" And beginners are responsible for debugging code written by veterans, which is what I assume you mean by "prime Developer"?

I would implement the composite index. It's not an unnecessary index, is it? It serves a purpose, so your question really would be, is it necessary to ensure duplicate records don't exist or not. I can't speak to the idea of using a trigger in the context you describe. Either way, you can't...

This thread veers towards a practice that I am all too familiar with, and which I now try to avoid as much as I possibly can. That is, trying to put wads of code into multiple form and control events in order to bypass, or to overcome, or to counteract, or to outwit normal Access behaviors. I...

Cool. We all have a lot of options for remaining connected. This has, unfortunately, drifted away from the original topic of the discussion, which was "I would be intrigued to know what other back ends our contributors may currently use?" One response was about using PowerApps, as well as...