Search results

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...

Good point. So if you have both a phone and a tablet, that is another option you can use that combination to get connectivity. The main difference, I guess, is one device (cellular enabled tablet) to carry vs two devices (tablet + smart Phone). The point I was really trying to make, though...

Interesting. Here's what Claude told me: Phone Link is a Microsoft app that connects your Android phone or iPhone to your Windows PC, letting you access your phone's features directly from your computer. What it does: Messages: Send and receive text messages from your PC Calls: Make and...

Are you saying that the Phone Link only connects tablets to smart phones?

Good question, I assume so. But that begs the question as to whether, being connected through Windows Phone Link, the smart phone gains access to an internet connection.

Thank you. The relevant factor here is that, with a cellular enabled tablet, or a smart phone, a user can run a PowerApps app regardless of whether they are connected via WiFi to a network or to the internet or not. The smartphone provides the connection. This is in contrast to the availability...

Feature Cellular-Enabled Tablets Non-Cellular Tablets Internet Connectivity Can access the internet via cellular networks Depends on Wi-Fi for internet access Mobility More mobile; can use data on the go Limited to Wi-Fi availability Cost Generally more expensive due to cellular features...

Perhaps I chose the wrong way to describe the difference I'm pointing out. I distinguish here between a cellular connection through a phone while not connected to the internet via Wifi and an internet connection via Wifi to an internet host or to a network. For example, I can connect my iPhone...

And how is db defined?

What exactly is the error and error description?

You didn't call out what I consider to be the primary benefit of this architecture. That is that a PowerApps app, linked to SharePoint Lists and running on a smart device -- phone or cellular-enable tablet, does not require an internet connection. Your ERP is not just online; it's available...

Good point. Essentially what you are passing here is very close to the structure of a Stored Procedure. CREATE OR ALTER PROCEDURE sp_UpdateCompanyType ( @iComp AS INT = 4, @iCompType AS INT = 2 ) AS BEGIN SET NOCOUNT ON UPDATE tblCompany SET CompanyType = @iCompType WHERE...

The data in views may or may not be editable either in SQL Server, via SSMS, or when linked in Access. It depends on how the view was created. The same is true of SELECT queries in Access, btw. The data returned by a SELECT query may be editable or not. I wasn't as thorough in discussing...

Um, while it is true that Pass Thru queries are read-only in Access, and that the term "Pass-Thru" means that the ACE engine is by-passed, I'm not sure the conclusion reached in your first statement is accurate. As you note, Access sees the linked view as just another table, and an Access query...