Recent content by Accessable

Are you trying to use a control as a subform? You must use a form. The third page of a tab control is still part of that tab control. Maybe I'm mixed up here, but I suggest that you make sure your subform is an actual form rather than a control. Then let me know if you still have problems.

You can use code that, upon receiving an error, will bypass the system message you're receiving. Put this code in the 'On Error' event of your form. A message box should show if you get an error. The message box will give the error number. Then you can edit the code to bypass the error. Let...

One other point: Lots of the standard things done in coding can also be done using macros. Macros can use conditional statements (if this is true then do this...) as well, and are easier to understand for people who don't code as much. You might try using macros to do what you want to do...

Try creating a command button, and putting your code in its On_Click event. Click it and see if the color changes. If the color changes, then you probably don't understand how your events are working (ex: When After Update executes). If the color does not change there's still some problem...

When I started out, I didn't understand how to use fields from several tables on one form and it drove me nuts! Queries have eased my troubles. I make a query that contains whichever fields I want from any table and base my form on it. Plus all the bonuses Jack mentioned. Ahhhh, isn't it...

Try: forms!frmMainForm.Form.subSubForm2.requery where frmMainForm is the name of the subforms' parent form. and where subSubForm2 is the name of the second subform (detailbox I think). -Mark

You need to use DLookup. This built-in function goes through all the records in your table and checks the specified field. It looks for whatever you put in the criteria (in this case table field must equal the form control value). If it finds the search material, then it does whatever you...

As far as I can tell, 255 is red. I code a little differently, though. I'd probably do this: Me.txtYourTextControl.BackColor = 255 Anyway, I don't think that matters. My guess is that you are never reaching this code. By that, I mean that your if statement is coming back as a False and...

Yeah. You see, this is done with coding. But Access makes this easy for newbies by doing all the coding for you. After the button is added, if you use the wizard as suggested, look at the Event tab of the properties window for your new combo box. You may notice that the On Click event has an...

Did you use a wizard? On your toolbox make sure the magic wand tool is pressed. Then add a combo box to your form. This should make the process simple. If you did not use the wizard, this may be a problem: It is possible that your combo box is not pointing to the table where your data lies...

This all should be done with coding. Are you familiar with coding? If so, what you need to do is use some conditional statements to analyze your data and set the values of your fields depending on the data. I'll assume you're only showing data for one record at a time (no list boxes/combo...

See my reply to Hayley Baxter "General Advice on Forms". In your case, you might try a combo box, command buttons, or option buttons. If you need help with the code, then let me know.

What I personally like to do is have a command button or toggle button on my form that locks/unlocks any worrisome fields. I do this with code. When the user clicks the button, I set the locked property of each field I want to protect to yes (locked). I also put in some statements that if the...

Put this in the AfterUpdate event proceedure of your first text box. Me.txtYourTextBox2 = Me.txtYourTextBox1 Reply if you need more help.

The reason for the error is that sometimes when you delete a control that has an event procedure written in code, Access just deletes the control and leaves the code. My guess is that you have made a control with a wizard and assigned it a name like "cmdOpen". Then you deleted the button...