Editable text box on MS Access 2010 - Behavior correct? - forms

I have a continuous form which displays an overview/summary of my data. A user can select a row and click a button I created in the footer to open another form which has all the detail for that particular record and be able to edit it. This works fine. However I would also like for certain fields to be editable from the continuous form. I enabled two fields I would like users to edit directly (One is a combo box selection and the other a text box) When users click the combo box for any record it works fine and they can go back to the same record and select another value if they wish. All great but the text box behaves rather differently - The text box will allow the user to initially enter a value but after entry the box appears disabled and the only way to change the initial data entry is to go into the detail form which still works. Why can't users change the text box from the continuous form after an initial entry?

I found the issue!
There was a conditional filter on that particular field

Related

Access 2016 Prevent "change" event from firing

I have a combo box in an Access form with 2 values Yes / No. The user opens the form and enters the reference number and pushes a button to run a macro. The macro executes a query to return data based on the reference number. The results of query are displayed in various text boxes.
After the combo box is built, the macro selects the appropriate value based on the query. The problem I'm having is that the "change" event is triggered because the combo box is loaded for the first time. I want to prevent this.
After reviewing the data, the user can choose to change the value in the combo box. At this time, I want the change event to fire because the additional macros are run that update multiple tables in the database.
Can I prevent the "change" event from firing when the form is loaded with data but allow it to fire when the combo box is changed?
Thanks in advance for any help or suggestions you provide........

Taking a Word document out of design mode

This should be a really simple thing that for some reason I can get to work.
I have an MS Word document which has a drop-down field. If I double-click it - a dialog comes up to add or remove things from the drop-down field.
I just need to be able to get out of this mode so that the drop-down field behaves like it should from a user's point-of-view rather than from a design point-of-view. Basically I just need it to display the items rather than a dialog to allow me to add and remove the items.
According to what I've read, it looks like I should be able to do this by going to Developer, and then toggling the Design Mode button. This doesn't work; whether the Design Mode button is on or off I still can't get it to just act like a drop-down.
Thanks much
It sounds like you're using a legacy form field dropdown. For those to operate as a dropdown, you must protect the document for forms:
On the Developer tab, click on Restrict Editing. The Restrict Editing task pane opens.
In the task pane, check the box beside Allow only this type of editing in the document.
In the next dropdown, choose Filling in forms.
Click on Yes, Start Enforcing Protection.
Protected forms don't allow text to be edited in protected sections. In those areas, only form fields allow you to enter text. If that's too restrictive, look into Content Controls, which don't require document protection.

Setting Widget Focus in Gtkada

I'm trying to create a simple test program in Gtkada to bring up a Dialog box upon leaving a specific textbox. I have managed this part, but am having problems resetting the focus back to the original textbox when the Dialog's 'Ok' button is pressed.
The general idea is that the user enters something into a textbox and when they click/tab out of the box (focus out event), some simple Alphanumeric validation is done. If the validation fails, the user is warned with a Dialog, and focus is returned to the textbox they entered erroneous data into.
All I am after is a simple example of how to set the focus back to a textbox when you close the Dialog box which clicking out of the textbox originally called. In Gtkada... I'm using version 2.2 of Gtkada. I can't change the version of Gtkada, or use a different program or language!
Much obliged!
Tim
The most elegant solution, GUI-wise, is to do the validation on a leave_event on each input field, and if that fails display an error message (in red or some such) next to the field. But do not display a dialog or force the focus to a specific field, that would interfere with what the user is trying to do (imagine: I enter an incorrect email address, press tab, get the dialog which I do not read (like most users), start typing my name for the next field, but since the focus went back to the email address, I have no overridden that one and lost my previous input).
If you still want to grab the focus, Gtk.Widget.Grab_Focus is the procedure you want.

Enable 'submit' button only if a value in the form has been changed

I have a php form for a website containing text fields which display values retrieved from my database and also a submit button. I would like the submit button to be disabled by default and to only be clickable if the user has made a change to one of the text fields in the form. However if they were to change it back to the default value, the button would automatically be disabled again. Any help is appreciated.
You need to use javascript. For each field, you must make a eventhandler that checks the value and then enables or disables your submit-button.
Declare a Variables for each Text box
Then assign the values that you Retrieving from database to the text box and a Variables...
At the time of Button_Click compare the Value of text box with the Variables
If BOTH are Same then there is no EDIT's occur
That's all

Issue with iPhone Keyboard Next and Input Field Focus

I am building a little registration page that is going to be accessed via an iPad at a sales office as a kiosk. When I first received the page from the web design company I noticed that the way they set it up was the labels of the input fields appear inside the field (like a watermark). The watermark is cleared out once you focus on the field and then restored if there is no value when you blur off the field.
I noticed that they had a couple password fields in the page that was showing the words PASSWORD and RETYPE PASSWORD in them. I don't want people's password exposed in the Sales Office, however changing the fields to type password means that the watermark labels become masked.
Since they were using jQuery to do the watermark in the input fields, I found another jQuery solution that would swap out the TEXT input field for a PASSWORD input field on focus. When I tested it on my PC in Safari it worked like a charm. However when I was testing the page with my iPhone I noticed that the jQuery field swap on focus only works if I click on the field with my finger. If I am using the on screen keyboard and clicking NEXT to get the field, then the field doesn't get swapped and the on screen keyboard goes away. I have to physically click the field to get the swap to fire. Is there some other even that I can use to trigger the swap instead of focus?
$('#txtRetypePassword-clear').focus(function() {
$('#txtRetypePassword-clear').hide();
$('#txtRetypePassword-password').show();
$('#txtRetypePassword-password').focus();
});
Of course as soon as I posted, I did a little more reading on DiveIntoHTML5.ep.io and saw that HTML5 supports "placeholders" so I thought to myself, I wonder if you can put a placeholder on a PASSWORD input field. YOU CAN!
So I get to rip out all that jQuery because HTML5 supports everything the page was trying to do!