Search results

This is a great idea. I like RichMorrison's idea about the different types of dB we could build. Also, how about at different skill levels. You know: 1. Basic (newbie) 2. Intermediate 3. Advanced I'm sure that everyone could get some use out of them. I know that I've gotten use out...

Well, since you don't want to use a query, you could do it this way. Create the pop-up form with a series of unbound text-boxes (as many as you need for the data). Then on the pop-up form, use the DLookup Function to populate the textboxes. Example: DLookup...

You can also set the Allow Additions property of the form to Yes and the Allow Edits property to No. This will pull up the form to only allow a new entry. Alternatively, if you are opening the form from another form via a command button, you can set the property directly in the VBA code...

Fuga's solution should work. If you want to close the Parent form, try inserting a docmd.close statement after the child form has been opened and the parent id value inserted. Docmd.openform "childform",,,,acformadd forms!childform.parentID = me.parentID Docmd.close I'm not sure if this...

Here are some links that you may find useful: An Access Tip site that sends tips to you via e-mail: http://www.elementkjournals.com/tips.asp A free newsletter: http://www.larkware.com/MailingList/signup.aspx There are a couple of others out there. Just surf for Access related sites.

Or alternatively, you could also change the code from before to: with forms!frmHd .cmdNewRecord.enabled = False .allowadditions = False End with That should do the trick. I'm not sure how to disable the toolbar button, but I think that the .alloweditions thing should work even if the...

Put this after your code: DoCmd.OpenForm "frmHD", acNormal, , , acFormAdd Forms!frmHd.cmdNewRecord.enabled = False Make sure to replace cmdNewRecord with the name of your command button that allows a user to create a new record. This will disable that button. HTH

Another way of doing this is to do the following: Create an option group with two options (toggles, radio, check, etc...). The option values should be 1 and 2 when they are created. Create an unbound text box that will be the search criteria. Create two queries, one to search for the...

I had a similar problem. I would open a form from another form in order to edit information. Then when I closed the first form with the DoCmd.Close statement it would close the second form and then also close the first form. It turned out that I had a DoCmd.close statement on the first form...

You don't need a macro to make this happen as the code above should work fine. My guess is that you either do not have the code placed in the "after update" event of the check box control or you are not referencing the names of your controls properly. First, make sure that the code is in the...

It seems to work fine. Thanks for the help. I never would have thought of that!

I do it that way, however that makes me have to build seperate queries for each form. What I'm trying to do is pass the form name, along with the text box name as a parameter to the query. This way, two (or 5) different forms can use the same query, just passing the name of the form with the...

I don't want to limit the records viewed by the user in that way. What I have is several department heads that have different categories of items that they use. What I want to do is let them enter search criteria and click on a button that will pull up items in a list. These items need to be...

This may be a simple problem, but I'm stuck right now. I have two different user forms. They each have a text box called strSearchCriteria. What I want to do is run a query based on the value of the strSearchCriteria box. I further want to limit the results of the query to be items that are...

There are a couple of other ways to try to correct this. I've had luck requerying the list using the Activate event of the form with the list. When you close the updating form, the list form becomes active and requeries the list. Another thought is to requery the list using the Click event...

Figured it out. Basically, I had enter code to save the record before I closed the form. Then the error trapping worked. Now everything seems to be peachy. Thanks for your help.

Form already has those properties set. Further clarification: User chooses an item from list on main form. Clicks button to place new order. This opens an order detail form with the item information already filled in. The user then enters the quantity needed and clicks a "Place Order"...

I'm having a similar problem to other ones that have been listed, but mine is slightly different (at leas I think so). I have a table that uses three fields as its primary key: dtmOrderDate strUser strItem Basically, it is to make sure that the same user does not enter orders for the same...

Rich, Thanks again for the input. I'll give it a whirl.

Rich, Thanks for the input. I can understand the crosstable query, but is there a way to get this to print in this manner on a report. Basically, what I have is an item with three different users. Everything prints fine in the detail section except that I'd like to get the three users to...