While navigating through tab key, the order of the focus is not maintained.
For example - If my table has four columns - A,B,C,D and tabbing into the grid is enabled, on pressing shift+Tab, the focus comes to Header C and not A.
The order of the focus does not seems to work
Related
I'm wondering if anyone has come across this issue.
I have two radio buttons on a canvas app that I am attempting to control the values displayed within a list box.
RadioButtons.Items: ["SomeValueA","SomeValueB"]
The list box control should be getting reset whenever the value of the radio button changes.
UpdateContext({resetList: !resetList});
UpdateContext({resetList: !resetList});
Reset(lbListbox);
lbListbox.Reset: resetList
For the list box itself I have the following for Items:
Switch(
RadioButtons.Selected.Value,
"SomeValueA",
Sort(
EntityA.FieldName,
Descending
),
"SomeValueB",
Sort(
EntityB.'Some other field name',
Descending
)
)
The problem is when I select 'SomeValueA' the list box properly populates with the values from EntityA.FieldName but when I then select 'SomeValueB' from the radio buttons the list box blanks out with empty records. There appears to be items in the list box that I can scroll through and select but not see.
If I put two list boxes on the screen and set their Items event to the specific entity the values show up properly in both list boxes so I know the entity naming/field is correct.
I've tried it without the reset of the list box, I've tried it using collections made out of the entity records.
Has anyone come across this who maybe has a solution. I was going to try to put two list boxes on top of one another and either hide/show or bring to front the active list but that also doesn't want to work.
thanks!
(Received this post from another source, figured I might as well post back here as well)
Got this to work, but it was a bit finicky. The catch seemed to be giving the List a value-pairing table, instead of just a list of values.
First I collected the Option Sets from CDS, and added a column to indicate the source name, for reference. This could easily be combined into a single collection, and then filtered later but I was thinking simple.
ClearCollect(colOptionSet1,AddColumns(Choices('Ownership (Accounts)'),"appSource","Ownership"));
ClearCollect(colOptionSet2,AddColumns(Choices('Preferred Method of Contact (Accounts)'),"appSource","Preferred Method"));
Next added a Radio button identical to yours.
Then added a List control with Items equal to
If( Radio1.Selected.Value = "SomeValueA", colOptionSet1, Radio1.Selected.Value = "SomeValueB", colOptionSet2 )
You may need to use the right-side property pane to toggle between Value and "appSource" (from collections above), but this did allow me to toggle between two separate Option Set fields in a single list.
Patching/writing this back is gonna be another hurdle. 😝
I created a tabbed form in Microsoft Access. The form has seven tab pages each tab page has a number of subforms. The problem is when I move from tab page to tab page the form opens in the middle of the page and requires scrolling up to see top of the form and the tabs of tabcontrol. From my search, I understand this can happen because the form is extra long. I do not want to resize the form as it has to be that long. I checked the tab order of each tab page and all controls are in the right order. My question is how can I force the focus to be on the top of the form when moving between tab pages?
I found a solution that worked for me. Putting a control at the top of the tab order list does not mean that you will get the focus at the top of the tab page. It seems that Access automatically put the focus on the last created control. What I have done is to create an unbound text box with width and height 0 - to be hidden - and I placed it at the top of my form inside each of the tab page. It is important to check that it is at the bottom of the tab order list in each page, job done!
I had the same problem and found an easy fix to it. I had 4 subforms on one tab page (2 at the top (order nr. 0 and 1) and 2 at the bottom (order nr. 2 and 3)). When moving between tabs and going back to my tab with all the subforms, Access just sets the focus in the middle of the page or, to be more precise, where subforms with order nr. 2,3 are.
After checking a million times the orders, I found this solution:
Select the subforms that are at the bottom (in my case the subforms with order nr. 2 and 3)
2.Go to properties > Other > change "In Order" to "No".
My form has a button "Process files", and when pressed, nested VBA procedures will be executed and a subform will display a table of ids and their associated results. My question is in order to display a table with mutliple rows in a format that resembles something similar to a datasheet do I create the subform with the Multiple Items Form or the Datasheet form. Some more specifications on the subform are:
Form Properties
Name: fsubInstrumentInterfaceLog; Default View: Continuous; Record Selectors: Yes; Navigation Buttons: Yes; Scrollbars: Vertical
Header, Detail, Footer
Header: Column headings
Detail: One row of data fields. fields set to Enabled = Yes; Locked = Yes.
Container Properties
Insert this form into frmInstrumentInterface with Subform/Subreport control
Parent-Child Link: Link Master Fields: BatchID, cboInstrument; Link Child Fields: BatchID, InstrumentName
Special Effect: Etched
Here are my thoughts between both styles of continuous forms.
Datasheets forms
Resemble Access tables and Excel spreadsheets.
Can be very wide or long with no limit (to my knowledge).
Individual rows and columns width and height dimensions are adjustable by user (not limited to designer).
Does not contain editable form headers/footers. However, datasheets do allow footer aggregates (Sum, Avg, Count, etc.)
Conditional formatting can be applied.
All trigger events by field controls can be applied.
Limited GUI objects and their events can be integrated (no labels, buttons, or list boxes, etc.). Combo boxes can be added though. But this may not matter if you use a main form.
Special effects, back color, border color, and other control designs not allowed.
Controls can be locked from user changes.
Record selectors highlight entire row like spreadsheet.
Navigation controls and scrollbars are enabled.
Parent-Child links can be established like any other subform/subreport.
Multiple item forms
Resembles a row by row form view of the data.
Limited to 22 inches in width and height.
Individual row and columns width and height dimensions are not adjustable by user but limited to designer.
Does contain editable form header/footer.
Conditional formatting can be applied.
All trigger events by field names can be applied.
Any GUI objects and their events can be integrated (labels, buttons, drop down fields, etc.). But this may not matter if you use a main form.
Special effects, back color, border color, and other control designs are enabled.
Controls can be locked from user changes.
Record selector limited to arrow at far left of record.
Navigation controls and scrollbars are enabled.
Parent-Child links can be established like any other subform/subreport.
Overall, both operate very similarly. For me the choice depends on functionality of your form and subform combination. Multiple item forms provide a more natural user interface that be consistent with other forms. Datasheets can disrupt such a UI but they are easy setup for large volume.
I have a HTML Table with 5 rows and 5 columns. Now when the user starts filling in the Data, and wants to navigate from One cell to another, they clicks on tab and the cursor moves horizontally.
Instead of Horizontal, I want to move vertically. Like shown below in Image. This is very tricky as we want to override the basic OS? Browser functionality.
The global attribute tabindex:
The tabindex content attribute allows authors to control whether an element is supposed to be focusable, whether it is supposed to be reachable using sequential focus navigation, and what is to be the relative order of the element for the purposes of sequential focus navigation.
The value must be an integer (you need values greater than 0; see the linked spec for details).
One way to do it is to use javascript onkeypress events to then give the next cell down focus. onkeypress="if(event.keycode == 8) {document.getElementById('NEXT CELL DOWN').focus()"} In this example 8 is the tab keycode. NEXT CELL DOWN could be hard coded for each cell or you could use an algorithm based on the current cell ID to move it to the next cell ID. For instance if tab is pressed on cell 1 the next cell could be cell1++. Does that make sense?
I can't seem to figure this out. I have a subform displaying continuous forms with a vertical scrollbar. When I click the scrollbar to move to a different record, the record never receives focus. The focus is still on the control of the record I left.
How to I control the record focus after using the scrollbar? The subform's On Current event does not fire.
Thanks!
The vertical scroll bar in a continuous MS Access form does not navigate among records. It simply changes which records are visible on the form. The black triangle within the record selector on the left side of the form indicates which record is currently "selected."
You can navigate records (ie, control the record focus, as you say) several different ways:
Click on the record selector* (the gray rectangle to the left of the form detail section)
Click on any enabled control within the form detail section
Use the navigation controls* at the bottom left of the form
Use [Tab], [Enter], or arrow keys to move through the individual controls on the form detail section; when you reach the last control in the tab order, your next [Tab]/[Enter]/[Down Arrow] key press will take you to the next record
* Note that both the Record Selectors and Navigation Buttons may be turned off on your form. On the form property sheet, ensure Record Selectors: Yes and Navigation Buttons: Yes.