One of the biggest pains is when you have multiple back ends and Linked Table Manager (LTM) prompts you at every table. When you have lots of links and multiple back ends, it's a pain to go through and select all from only one back end.

Idea #1: Click on a single table in LTM, then click a button: "Select all tables from same back end." Voila! Now you can update that single back end, and then move on to the next one.

Idea #2: Sort the tables by back end. Not as convenient as Idea #1, but would still make life a heck of a lot easier when you're trying to update links from multiple back ends.

Ideally, what would be best would be to able to select all tables, and just have LTM prompt you once for each back end location. But that would require rewriting the code a bit, I get it. The above two ideas are both very simple to implement without having to rewrite the existing code.

Given the fact a decision on AWA has been taken, here's I think what the development team should do. 1. Make AWA datamacros available in Access Desktop 2. Extend with support of Update/Create/Delete Queries in the query designer. 3. Explode functionality by making datamacros that return just one value available as functions within expression builders of queries and datamaros 4. Support the database qualifier in front of tablenames the way it is already available in SQL-Server between databases. this way users can integrate AWA managed and non-AWA managed very easily. (integration with CLR SQL-server projects and other tools that generate Stored Procedures (LinqToSQL). This way all SP_ functionality in SQL-server (which spans as much as Powershell does (encryption, certificates, you name it and it's there) can be made available to Access Projects. 5. Provide for a proper connector to PowerApps/Flow that is aware of AWA managed databases (and their connectivity with each other and unmanaged databases.

I recently updated my computer to Windows 10 version 1703 and since then embedded objects in Access forms and reports do not display properly (cannot be seen). When Windows is downgraded to its previous version the problem disappears. The problem occurs with Access 2010, Access 2013 and Access 2016 (all 64bit).

To demonstrate the problem do the following:

1) Create a blank Access Desktop Database (Database.accdb).

2) Create a new table (Table1) within the database.

3) Add an AutoNumber field (ID) to Table1

4) Add an OLE Object Field (Document) to Table1.

5) Create a blank form (Form1) within the database and set the Record Source for the form to Table1.

6) Add a Text Box control (ID) to Form1 and set the control's Control Source property to ID.

7) Add a Bound Object Frame (Document) to Form1 and set the control's Control Source property to Document.

8) Open Form1 and add ole objects to Table1 by right-clicking on the Document field and selecting Insert Object.

When a Word or Excel object is added it appears in the Document Frame and additional records can be added using the Record Selectors and Navigation Buttons.

When using the Record Selectors and Navigation Buttons in Form1 to move through all the records in Table1, the embedded objects associated with each record should appear in the Bound Object Frame control (Document). Once Office 10 version 1703 has been installed this no longer happens. The same error occurs for both Excel and Word objects.

Some VBA/Office library methods throw errors.

For example, Application.LoadCustomUI throws error 32609 (Access 2007-2013) or 326010 (Access 2016) when the ribbon has already been loaded. Forms.Item throws error 2450 when there is currently no open form with this name. The "/" operator throws error 11 when a division by zero is attempted.

These error codes should be documented with the method that can throw the error. For an example of how this could be done, have a look at the documentation of the .NET Base Class Library: The documentation of every method has a section "Exceptions", listing all exceptions that can be thrown by an invocation of that method and the circumstances under which the exception is thrown.

In Access 2016, I have a database with Access File Format 2007-2016 and Database Sort Order "General".
I have the following data in a table with Short Text field "TestColl"

TestColl
--------
Aehnlich
Ähnlich
Baer
Bär
Froehlich
Fröhlich
Fruehling
Frühling
Oesterreich
Österreich
Ueberhaupt
Überhaupt

These are 12 rows. Now I run a Select Distinct query on this field. This results in only 10 rows:

TestColl
--------
Aehnlich
Ähnlich
Baer
Bär
Froehlich
Fröhlich
Frühling
Oesterreich
Österreich
Überhaupt

Access has identified "Fruehling" with "Frühling" and "Ueberhaupt" with "Überhaupt", but it did not do this with the other umlauts "ä" and "ö".

To me, this seems to be a bug in the collation table.

Furthermore, using Sort Order "General - Legacy" returns all 12 rows, and Sort Order "German Phonebook" returns six rows as expected, identifying ä = ae, ö = oe and ü = ue.

Matthias Kläy, Kläy Computing AG