We are a small firm. We do not use client ID's for anything. You should have a feature, or box to check, for small firms that don't use IDs to check so that we do not see them on any reports that print. It looks terrible to see a client ID that was created for a client on a report that will never ever be used. You should have the box on the Primary Contact screen to suppress IDs when creating new clients OR a box when running due date reports to run to mark x to not see/use the client ID.

Non sto parlando dei titoli dei programmi che funzionano da Comandi, ma di qualsiasi altra scritta o immagine presente. Ciò mi sembra che dipenda dal fatto che adesso non c'è più la possibilità di "stabilire" quale pagina farà da apertura per l'intero programma, mentre nelle prime edizioni si poteva scegliere. Se lo stesso programma si "manipola" con Windows 7, ciò non succede. Io da oltre 20 anni costruisco programmi successfully con ACCESS, non solo Data Base ma anche Giochi tipo Tombola, Gioco dell'Oca, Biglietteria and more and more, per cui sono "addentro" al programma, ma gli errori "strutturali" non li posso correggere. Danke, prof Blasius.

There seem to be several things missing in the new "modern" charts in Access. A couple of things I have run into include:

- The gridlines don't seem to work, nor can I find a property to set their color
- There doesn't seem to be a place to set the desired color for each bar of a graph
- There doesn't seem to be a way to modify the sort order (or any of the SQL) of the "Transformed Row Source", for example to sort the categories by descending value
- Can't find settings to vary the tick marks etc.

Maybe I'm missing something but there seem to be a lot of properties that could previously be changed that no longer can.

Opening/using forms that contain ActiveX controls, notably "Microsoft TreeView Control, version 6.0" cause Access to crash since at least version 16.0.11727.20210 on the Monthly channel. No versions in the Semi-annual (Targeted) channel seem to have this bug (yet).

The forms affected usually crash within moments of opening, but occasionally will work to some degree for several seconds.

Faulting application name: MSACCESS.EXE, version: 16.0.11727.20210, time stamp: 0x5d0d79e6
Faulting module name: ntdll.dll, version: 10.0.18362.1, time stamp: 0x9bbcb4a9
Exception code: 0xc0000374
Fault offset: 0x000df8cd
Faulting process ID: 0x50d4
Faulting application start time: 0x01d52cbe9164d25e
Faulting application path: C:\Program Files (x86)\Microsoft Office\Root\Office16\MSACCESS.EXE
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: c7ada4ee-be96-4c9d-ade3-47beaddc78d3
Faulting package full name:
Faulting package-relative application ID:

Versions we've tested that experience this bug:
16.0.11727.20188
16.0.11727.20210
16.0.11727.20224
16.0.11727.20230

Versions that work fine (so far):
16.0.11328.20318
16.0.11629.20246

We're using Group Policy to block the versions with this bug and instead installing 16.0.11629.20246

Computer Configuration > Administrative Policies > Microsoft Office 2016 > Updates > Prevent Office from being updated to a specific version
Enabled, blocked versions:
16.0.11727.20224:16.0.11629.20246|16.0.11727.20210:16.0.11629.20246|16.0.11727.20230:16.0.11629.20246

This Control would have a Modern Appearance that we see on a lot of Websites using the Bootstrap technology. When the User resizes the Application, it would respond and collapse to a hash icon of some type.

This Control would be Table Sourced, where the Developer could enter Custom Search Terms and then map it to an existing Form Object. A default could be set to inherit the existing Custom Category, or inherit the Parent Child Navigation Buttons on a Navigation Control. The Developer could Customize from there. The Possibilities are endless.

The built-in Navigator exposes too many objects to the end-user and is somewhat confusing to them.

I feel that if we have a Tree Control of a Modern Touch and Feel, where the Child Items would flow out as the User hovers their Mouse of the Parent Node.

Well with the recent push of 64bit Office and the problems that arise by the lack of the usual .ocx maybe its time for a step forward....how about Open Source the usual suspects like MsFlxGrd and the alike...its a fact that you have some brilliant controls over 20 years old that alive and kicking in 32bit but not in 64bit and A lot of developers are forced to get stucked in 32bit because they just work and they provide unparalled functionality ....so if you really want to push the 64bit and for any reason you can't develop the 64bit equivalents of these controls maybe you should leave it for someone else....
I am pretty sure that if this comes with a price bonus...64bit Access will be fully functional in a mater of months