I have a MS ACCESS 2007 form with 2 subforms. I have a few fields from the main form as text, a few on the second form as text, and a lot on the third form as a variety of things.
My problem with these subforms, when I am entering data in the main form, my mouse scroll works just fine to scroll to the bottom of the form. When I am in subform 1 or 2, my mouse scroll stops working to scroll down to the bottom of the main form. I tried looking up disabling mouse scrolling but that's already preset for a single form view in MS Access 2007. I just want the mouse scroll to work only for the general form even if you are doing data entry into subform 1 and 2.
I know it's been a while since your post. But I've had nearly the same problem and figured it out, so thought I'd post the answer anyway:
If you make an extra textbox in your main form (make sure it's property visible is set to TRUE), then place this textbox behind any other control so to the user it seems like there is no textbox.
Now in the properties of the details selection of the mainform make an onClick event (this occures when you click anywhere in the mainform). In this event use the SetFocus method which redirects to the textbox made earlier. The code looks like this:
[Forms]![MAINFORM]!TEXTBOX.SetFocus
If you click on the form (outside the subforms) the textbox gets selected automatically, which allows you to scroll the main form. The user doesn't see the textbox so it seems as if he/she selected the mainform.
Hope it helped!
Related
I have a full-screen form (using popup) which contains a button that launches a child form. I read that I have to set the child form as popup to make it stay on top. I've done that, but it is still not working. After more googling around, I found out that it's not working because the parent form is also set to popup. How to solve this problem with maintaining the parent form in full screen mode?
As I understood, you need to open child form and it should stay above main form. Both forms should be popup, but if the size of child form will be less than main form, user can click on main form and child form disappears under main one even if child form has Modal property. If you don't want this, just open child form with acDialog WindowMode parameter.
I have an update panel with some text entry boxes, a clear button and a save button. Under the boxes I have a repeater that holds database entries. When a user enters data in the textboxes and clicks the Save, a database row is created and the repeater rebinds and shows the new dataset. There are buttons on each repeater row for "Delete" and "Edit". When the Edit button is clicked on a row, the data from that row is populated back into the text boxes. When I do that, the autocomplete extenders stop working. I have a button that simply clears the textboxes. If I click that button and clear the textboxes, the autocomplete starts working again. Even if I remove all code from that "Edit" button in the repeater command and don't have it populate the text boxes from the row clicked, the autocomplete stops working. Something is happening on the item command for the repeater row that is turning off the autocomplete. Any suggestions?
I had some javascript functions running from the code behind on page load. Moving that from the server side page load to the javascript pageLoad() function fixed the issue
I have a main form...imagine that...that for most of my users will be the only form they use. Naturally, it contains tabs with sub forms.
I have a navigation sub form on the left side of this form that changes based on the user's rights level. Currently, this sub form is all buttons...and 1 always is selected as the default tab stop for that form.
I don't want to highlight any of them at first...and I can remove the highlight by switching off Tab Stops for all buttons. However, I'm not sure that I want to remove that functionality all together...and it still highlights a button. I'd just like for there to not be a default button highlighted.
As you can see, Add Course is 'selected'. I can't seem to find the correct terminology to search for a way to do this. I tried using a smaller button set behind another button, but since it has the focus, it moves to the front. Using a text field with the same colors as the background shows the cursor in a random, blank area...not visually ideal.
I'm sure that there is someone here clever enough to have this figured out. Please enlighten me. I don't care if this can be handled in VBA code or through design view.
"Focus" is the word you're looking for - you don't want any visible control to have the focus when opening the form.
The easiest method is an invisible button: create a button with Transparent = True, and an empty OnClick (i.e. the button does nothing, even when accidentally clicked).
Move this button to the top in the Tab Order, so it has the focus when opening the form.
But if your users use TAB to walk through the buttons, there will be one position where the focus disappears (when circling around from the last to first control). I don't know if it will confuse them.
Create a button on the main form itself.
Named is cmdDummyButton with the following GotFocus event code.
Set the tab order property to 0 (ie first)
Make the button transparent.
This will cause no control on the form to have the focus when it starts up.
Private Sub cmdDummyButton_GotFocus()
Static IveHadFocusAlready As Boolean
If Not IveHadFocusAlready Then
Me.cmdDummyButton.Enabled = False
IveHadFocusAlready = True
End If
End Sub
Sweet.
We can able to create lot of fields and forms using remedy developer. i just wanted to know whether any options for giving tooltip to those fields so that users can better understand over the respective field.
For eg: If there is a field say price, say tooltip like decimal values accepted or something reasonable.
Try to edit fields' "Alternate Text" attribute for a small tool tip.
If you want a bigger one like in overview console table etc., run AL log and see which AL opens it.
Hover option is available for ARS 7.6 or later, and here are some info for you from BMC docs:
Using the message action to create tooltips
Tooltips are brief informational messages that are displayed in response to a user action with an object on the screen. Tooltips are commonly used to provide descriptions of menu items, toolbar buttons, or other objects.
In AR System, tooltips can be applied to tables, attachments, field labels, or field data.
A tooltip can be displayed either by hovering the mouse over an area in a form or by clicking an object such as a button. For table fields, a tooltip can be displayed by hovering over a row. The tooltip displays the values for the row being hovered over, even if that row is not the currently selected row.
When a tooltip appears by hovering, it is closed when the mouse is moved outside the tooltip's border. When a tooltip appears by clicking (for example, when a tooltip appears when you click a button), it is closed when you click anywhere outside the tooltip's border.
A tooltip also can be dismissed by pressing the Escape key.
Tooltips can include URL links, which can be added through a Set Fields action.
Implementing tooltips
Tooltips are implemented through two types of AR System features:
HOVER event
Active link Message action
I am new in Microsoft Access. What i want is to switch between forms in subform panel depending upon the user selects from drop down list. Attach file contains what i want
I google alot but didnt find any help. Thank you for your help.
Here is screen shot. but I am confused in finding control of subform.
Forms("frmMain").Form.subFormControl.SourceObject = "SubForm_2_A"
..should be all you need.
subFormControl is the name of the subform-container-control that contains Subform2.
frmMain is the name of the parent form, not labelled in your picture (actually, you might not have to put subform1 in a subform really, its content could be on the parent form).
EDIT:
The red frame marks a subform. Click on -1- to make sure the main form has the focus. Then click once on -2- and the control is selected, and its properties show up in the properties box on the right.
Note that you find the "source object" in the data page and the name of the control in the "other" page. Access makes the name (of the control) the same as the form, which is really not such a bright idea and rather confusing.