Please fix the combo box RowSource datatype binding bug.

The bug is as follows:
1. Create a table [Table1] with two columns:
- [NumberField], datatype: Number, Double
- [TextField], datatype: Short Text

Add 1 Row to the table:
[NumberField] = 10
[TextField] = "Some Text 10"

1. Create a combo box:



2. Set the RowSource of the combo box to this:
   SELECT NumberField, TextField FROM Table1;




3. Add a Button to the form: [cmbErrorExample]
   Add On Click Event:
   If Me.cmbErrorExample.RowSource = "SELECT NumberField, TextField FROM Table1;" Then
   Me.cmbErrorExample.RowSource = "SELECT TextField, NumberField FROM Table1;"
   Me.cmbErrorExample.DefaultValue = "Some Text 10"
   Me.cmbErrorExample.Value = "Some Text 10"
   Else
   Me.cmbErrorExample.RowSource = "SELECT NumberField, TextField FROM Table1;"
   Me.cmbErrorExample.DefaultValue = 10
   Me.cmbErrorExample.Value = 10
   End If

Now open the form:
Drop the combo box, you should see the one row with values:
10 | Some Text 10
Select the row - the value of the field becomes 10.

Now, click the button. The Rowsource should change to:
"SELECT TextField, NumberField FROM Table1;"

However, if the user has already made a selection as instructed above, error appers:

Error Occurred in Sub cmdToggleRowSourceClick of Module FormForm1

Error The value you entered isn't valid for this field.

OK

Expected: the code should be able to programmatically change the Rowsource of the combo box.

Actual: Because the unbound field has had a numeric value assigned as a value, the programmatic change of the RowSource of the combo box to a text value results in a type mismatch that should not be happening.

This used to be possible in Access 2003, but in Access 2019 the combo box appears to change itself to be bound to a numeric data type, even though it is an UNBOUND field.

This is a problem when creating forms that change combo box data sources programmatically.

This URL contains a .accdb with a sample form that demonstrates the issue:
https://1drv.ms/u/s!AhezOlimTLoah-V27m77K4MRlU5loQ

My idea is similar to the one called "Provide a native grid control similar to the visual studio gridview or even the old flexgrid" EXCEPT I want it to be a BOUND crosstab that is editable. This blog describes how to fake an editable crosstab, but it is a lot of work http://alisadev.blogspot.com/2009/06/how-to-fake-editable-crosstab-in.html. My best example is that for a school, they want to view the grades in a grid, but be able to edit them. Classes go down the side, Quarters go across the top, and Grades will be in the middle. When the user is hand-entering the Grades for Quarter 2, the user wants to be able to see the existing grade for Q1 next to it. I could create this by dumping the data into temp tables and creating a crosstab view, but then it is not editable because the crosstab is not bound back to the underlying normalized tables. This is not summary data (like # sales per month per employee), but just data from normalized tables being presented in an editable grid. The solution / process would be to take the data from normalized tables, de-normalize it and present it in an editable crosstab (with maybe a temp table behind it), and then normalize the data again and save it back to the source tables.

1. When a query that selects identifiable rows joins to a query that aggregates data, allow rows in the identifiable part to be updated rather than making the query non-updateable. Extend this to heterogeneous joins so if one table in the join is updateable but another is not, allow updates to the updateable one.


2. Stop smothering expressions with excessive numbers of parentheses. There is no reason that I can think of that would require an individual column name to be enclosed all by itself in parentheses.


3. Stop reformatting MY SQL strings. I have a work-around for this but it is iffy. I switch to SQL view and save the query. As long as I never switch to QBE view again, Access doesn't normally rewrite my query but that isn't a guarantee.


4. Stop helping me by renaming all fields to Exprx when a table goes missing or at least keep track of it and fix them when the table is relinked.

I know it's hard to believe but there are a lot of us in the world (yes, even in the United States) that must occasionally work disconnected from a network. At our site we've nursed Jet 4.0 replication along for as long as we can and now it's starting to break as MS has backed away from supporting it. We are moving to a centralized SQL database with mobile hotspots but there are some places this simply will not work reliably. We will be forced to 'roll our own' replication method or bring on significant additional SQL expertise to see if it is even possible to reproduce our replication scheme using SQL. Jet replication worked great for us and Microsoft inexplicably decided to drop it.

My applications, a synthesis of MS Access and MS Excel using automation, are totally self-contained and use customized Ribbons, so Backstage on the Ribbon is a distraction for my users. If I could, I would hide it entirely, but that isn't possible. Until Access 2016 all Backstage elements could be hidden individually using XML, but with the introduction of the Feedback element in Access 2016, this no longer seems possible. It doesn't make much sense for a user of my applications to provide feedback directly to Microsoft, so I'm hoping the inability to hide Backstage Feedback using XML is an oversight by Microsoft that will be rectified in the future.