Ms access bound textbox not updating Free live adult chatrooms
Once the user does either of these options, I then need the txt Location ID textbox to update to the new Location ID of the new/existing location and also need the unbound textbox to update to the new/existing location. If it does, it updates the txt Location ID box (this all works fine.
It it doesn't already exist, the new dialog box pops up. The popup box has a textbox called txt Unsaved Loc, a save button for the new location called cmd Save, a list box populated with similar locations to the originally entered location and an ok button to select an option from the list box.
On loading, the list box is populated using a query where the unbound text box from the data entry form is tested using a Levenshtein function and produces locations with If the user selects an option from this box and then presses the Ok button, I need the selected option to populate the unbound textbox with the text and the bound textbox with the location ID. It replaces the unbound textbox but the bound textbox doesn't change.
The value is Cirencester, which is the text value I selected in the list box.
In turn, those design principles affect how you enter data.
Remember these facts about database objects and design as you proceed.
An Access database is not a file in the same sense as a Microsoft Office Word 2007 document or a Microsoft Office Power Point 2007 slide deck.
Following on from It's going to be complicated to explain but I'll give it a go and hope you guys understand what I mean.
So with this same data entry form, when the user enters into the textbox a location that is not already in my tbl Location, a dialog box opens up giving the user the option to add the new location to the table or to select an existing location from a list box. The first function below is what I am using to determine whether or not the entered location already exists in the table.
Thanks, all Scott, we have had some corruption before on the codebase so I'll try that.
Coach, good point, should have mentioned I'm already doing that, as well as making sure "Date" columns don't start with "date". The query is already drawing those fields from the database and I can see them as options in the dropdown list when allocating the controlsource property.