Ok, first the basic part - I have a couple of comboboxes, the second is dependent on the output of the first - simple enough. I then want to be able to disable the second combobox until text is entered into the first (being typed). This is normally done through the afterupdate event, or if you just want to make sure there is text in the field, it can be done on the Change event. In Visual Basic, I know that just the Change event is required, but in Access it does recognise any difference in the field after the first keypress - i.e. If you setup the code to make the combobox blank when the control is empty, if you press backspace to delete the text, the second combobox will remain active. I know that this is because, for example, when pressing a key and finding the length of the combobox box, the len of the contents doesn't change until after the update.
Therefore, my question is very simple, and yet at the same time quite difficult - where is the text that is being typed being temporarily stored? I have been tempted to do an array for the keydown events, but this won't help to much if the text is highlighted and then deleted.
If you are wondering why I am simply not content with the afterupdate property, it is because I feel that Access could look/react better if this type of code was created.
Cheers
Therefore, my question is very simple, and yet at the same time quite difficult - where is the text that is being typed being temporarily stored? I have been tempted to do an array for the keydown events, but this won't help to much if the text is highlighted and then deleted.
If you are wondering why I am simply not content with the afterupdate property, it is because I feel that Access could look/react better if this type of code was created.
Cheers
