Search results

Oh well, it doesn't matter. I found a different solution. But thanks to whoever created the original Cool Search db. I found it very useful.

Very nice. I am trying to get this to work so that when I click on a record in the listbox [Search3 in my case], that record is loaded in another form. I have a record ID field [ActivityID] that I want to use for this purpose. I understand that the current setup is for the record to be...

Could be. However, the code generated by the wizard for the comboboxes also uses "findfirst". And it runs without any errors.

Maybe it should have, but I swear it did not. What I posted earlier was simply my attempt to customize RO's code for my situation. The reason why I ended up with "find" is that in the VB editor, the help system did not offer "findfist" after "rst.", but only "find". And it did not offer...

I used the wizard to create a search combo box directly on the main form, and it created this code: When I compare that to the examples you have posted, the one thing that sticks out as being different is your declaring rst as recordset vs. the wizard declaring it/rs as object. Maybe that's...

When I replace "Find" with "FindFirst", I get an error on "FindFirst". Looks like my Access doesn't like that command either.

Thank you for correcting the Find expression. However, both with the versions for text and integer - I suppose with numbers in a text field I have to use text, but I tried the integer version just in case - I still get that error on rst.nomatch. :confused:

What version of Access was that for? In Access 2002 this generates all kinds of errors. I've changed a few things with the help of the wizard, but there doesn't seem to be anything that can replace the rst.nomatch expression - I get a "Compile error - method or data member not found"

I wish you had elaborated on this a bit more, I am trying to do the same, but am a lot more clueless. :)

Never mind, I figured it out. The problem was caused by me trying to do this with more than one textbox; looks like attempting to directly update the table from more than one textbox at a time is a bad idea and leads to conflict. Now I'm updating the queries my subforms are based on, and that...

Hello, Something weird happened to me - I have a form with continuous subforms and on it are checkboxes. When I click on one specific checkbox, a text box on the parent form becomes visible, where I can add text, which is added directly to the table in the AfterUpdate event. However, the...

Hello, I have never done this before, but I read that it is a good idea to put code that is used in several places in a module. So, I'd like to try to do that. I'd appreciate help in deciding what needs to go into the module, as well as coming up with a method of using it. Thank you. Here's...

I'll take another look at the datasheet view, if only to save space on the form, but here's the solution to my problem. May not be awfully efficient, but at least it's working: On my parent form: On my subform

Thank you for your suggestion. I shall take a look and see how difficult it is. Somebody else mentioned that an update query may work, so I'll try that as well. Which of those methods would be better?

Hello, How can I save an unbound text field directly to a specific record in a table? I can specify the right record via recordID and questionID. The field I want to save to is called "Note". Right now I am moving the content of the unbound text field [located on the parent form] to a hidden...

Btw, how do you hide the main Access window?

Sorry, I don't know a way. But you could try to put a timer on your form, so that it minimizes by itself after a [short] period of time.

Why is it so difficult? It's on working when you put your code in the On Lost Focus event? Actually, that does work, because when you click on another window in the database, and the form loses focus, it does minimize. But I guess you want the same effect you get when it expands, in other...

Ok, thanks. I'll be playing around with the datasheet view a bit, but unless I can find a way to get rid of the column headers and the record selector, I can't use it.

Very cool. :) The first part - to position the window - is actually very easy. You can use an autoexec macro, and use the action MoveSize. You simply specify a value of 0 for both the Right and Down arguments, and the window will end up in the top left corner of your database window. First...