Search results

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

I'm not suggesting you try what was described. I'm suggesting that, since you are embarking on a new direction of development, there might be useful information available in that discussion regarding interactions with IoTs.

I'm sure that you can't create relationships on fields of different datatypes. I just successfully created a query joining two tables on a tinyint field and a smallint field, though. It made no sense logically in this test scenario, but SQL Server didn't object, since both as integers...

You might get some ideas from this YouTube video. It was a presentation on using and Azure IoT Hub with SQL Azure, but it has an extensive discussion of use of the IoT devices involved.

I won't share all of the details about why I know this to be a true statement, but it does involve a significant volume of curse words and keyboard practice while retyping those code changes.

Oh, in that case, I truly believe you are wasting time and effort to save some space that doesn't need to be saved. I can definitely see doing something like that in a green field database where you don't have to manage existing architecture and data and the motivation of saving spaces is...

I too am curious about the need to convert the datatypes of fields involved in Foreign Key Constraints.

Initiative: An organized effort by a group or groups to achieve a common goal. Trend: A prevailing tendency or inclination with no specified goals. What is actually happening with Access? Is it a trend or an organized initiative?

The situation has been greatly complicated by the recent censorship Online Safety Act laws in the UK.

Thank you. You have indeed proven something, even though you probably didn't intend to do so. Perhaps someone does have time and the inclination to replicate the line numbering function in one of the commercially available Access tools (MZ Tools, VBE_Extras, and perhaps others) for you.

And with that you just made my point :rolleyes:. You started out by asking other people to do the hard work of coming up with VBA code that replicates something already in existence. And you end by asking other people to do the hard work of trying to track done something that we suspect...

One last time. Show us the examples of your contributions, please. Links are fine.