PopUp forms do not get focus, because they are not intended for data.

I have read that plenty of times and know perfectly that is by design.

But to use a PopUp form is the only way to go out of MDI boundaries, sometimes it could be practical to open data in a Popup form, and do not know why that should lead to a focus nightmare, in which a lot of events and functions cease to work or change his behaviour.
It will very nice if we could forget that old assumptions about popups, getting in it the common focus functions.

Thanks

Pd.: One of the most annoying problems is the impossibility to "freeze" the form while code is executing, because Popups do not respond to Application.Echo False and to cancel Painting is not the same.

You probably should have a category, just for Access Charts, but anyway....
Using Dates in the chart comes up as numbers, and as such, the graph always shows up with lines starting from 0 instead of the minimum date. I know we have a minimum property, but Excel understands dates and it would be nice if Access could do the same.
Stacked bars swaps the x and y, so when I want to assign a field to the X line, I have to add the field into the Y list, and visa-versa. This is somewhat frustrating.
Also, can we have a Reverse Order option because I end up having to write one query for a form I'm using, and then having to create another query with a different ORDER BY for the chart. Seems an overkill.
Lastly, I would love it if the chart title (or subtitle) could make a reference to a form text box instead of having to use the forms OnLoad or OnCurrent event to update it.
Thank you

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

I purchased Office 365 Business so that I could use Microsoft Access. As it stand the application does not work as designed. When you go in to Form view you see limited fields. When you go in to design view you can see more of the fields. I've spent several hours with Technical support trying to resolve the issues with no success. The problem as explained to me is the Home Inventory template is not compatible with Office 365. So my thoughts is why is if available as a template if it's not compatible. I would like to see the issues with the template resolved.