Replies

Your reply prompted me to look at the data in the table I was going to use on the one side of a one-to-many relationship between stu-sr (section resource) and stu-abc (grading). This is a very large database made up from data extracted from a mainframe hierarchial system. Apparantly there are instances where a grade will be recorded (abc-record) without having a section resource record (sr-record). At this point I’ve decided not to pursue trying to use the referential integrity.

The initial error message made it sound like an index problem between the stu-ab and stu-abc records, but I guess the data is evaluated all the way down before it will put on the relationship (??). I’m sure the problem is more related to the stu-sr data. Thanks for everyone’s help.

Thank you very much. That worked. I SWEAR I tried that, but I must have changed something else in the meantime. Thanks so much for your quick response.

I figured out how to declare this and it works now.

Dim objMessage as CDO.Message
Then when I do the set I don’t get an error, and the emailing is working fine.

thanks.

I’ve just started to use CDO to send a group of emails from Access. I get a compile error on my CreateObject line. I added the reference Microsoft CDO for Windows 2000 Library. Is there some other reference that needs to be added? i didn’t see any other CDO related ones.

The compile error I get is “Object required”. My line looks like this:
Set objMessage = CreateObject(“CDO.Message”)

I’ve tried dimensioning objMessage as string. There really is no other type that shows up that looks like it would apply.
Also, I’ve seen references in posts to CDOnuts (??) or something like that. Is that different?

Any ideas? Thanks.

Thanks for posting this again!

I changed the code in this sub as you suggested and it works great. Thanks again.

I moved it around and even tried setting the warnings off inside the if, but I still got the “domenuitem” message after my message box. I started wondering if it had something to do with the docmd in the sub for the save button on the form. When I looked at that code the error handling had a msg box. When I commented that out it worked fine.

Private Sub Command80_Click()
On Error GoTo Err_Command80_Click

DoCmd.SetWarnings False
DoCmd.DoMenuItem acFormBar, acRecordsMenu, acSaveRecord, , acMenuVer70
DoCmd.SetWarnings True

Exit_Command80_Click:
Exit Sub

Err_Command80_Click:
‘MsgBox Err.Description
Resume Exit_Command80_Click

End Sub

Thanks for your help!! I’m the only one here using Access and without this bulletin board I would have no resources to go to. Thanks for responding so fast.

Private Sub Form_BeforeUpdate(Cancel As Integer)
Me!Checkchange = True
Me!txtuserid = Forms!frmdept!Text11
Me!txtuseriddate = Now()
If Me!holdadd = True And Me!Check83 = False Then
Me!Check83 = True
End If
DoCmd.SetWarnings (warningsoff)
If IsNull(Me!Combo88) Or Me!Combo88 = ” ” Then
Call MsgBox(“Course Number is required”, vbInformation, “Master Schedule”)
Me!Combo88.SetFocus
Cancel = True
DoCmd.SetWarnings (warningson)
Exit Sub
End If
If IsNull(Me!SR_SECTION_NUM) Or Me!SR_SECTION_NUM = 0 Then
Call MsgBox(“Section Number is required”, vbInformation, “Master Schedule”)
Me!SR_SECTION_NUM.SetFocus
Cancel = True
DoCmd.SetWarnings (warningson)
Exit Sub
End If

Me!SEQ = Nz(DMax(“[seq]”, “extractdata”, “[sr_course_code] = ‘” & Me.Combo88 & “‘ and sr_section_num = ‘” & Me!SR_SECTION_NUM & “‘”), 0)
End Sub

Yes, thank you.

If IsNull(Me!SR_SECTION_NUM) Or Me!SR_SECTION_NUM = 0 Then
Call MsgBox(“Section Number is required”, vbInformation, “Master Schedule”)
Me!SR_SECTION_NUM.SetFocus
Cancel = True
DoCmd.SetWarnings (warningson)
Exit Sub
End If

I found this post which was exactly what I needed. But…

After my message comes up about the field being required, and I try to send them back to the form, I get this window that say “The DoMenuItem action was canceled.” Is there any way to avoid getting this window? I’d just like them to click ok. on my message window and take them back to the required field on the form. I tried putting in a docmd.setwarnings (messageoff) in the vba code, turning it back on after the cancel, but that didn’t work.

I’ve attached a copy of the message.

Thanks.

Thank you! That worked great!!

Thank you so much! This has been driving me crazy, and this is exactly the reason. Works like a charm now. Thanks again.

Thanks for the info from both. I’ll check them out and post back if my problems aren’t identified.

Thanks for the info from both. I’ll check them out and post back if my problems aren’t identified.

You can only use the auto tab on text boxes. So I guess I would create the combo box as unbound, and create a bound text box right next to it that is part of the tab order. Take the tab stop off of the combo box. Put an input mask and auto tab in the text box. It sounds like they’re probably going to know what they want to type in anyway, without using the drop-down from the combo. If they do use the combo, put an event in the after update to set the text box equal to the combo box. You could also add an event to the text box to check for valid data if you want it to limit to the list in the combo box.

That’s what I’d do anyway, but I’m usually finding my own strange ways to do things. I did try it on a small form with 3 fields. With everything autotabing it goes to a new record after the last field. If you want to force them to save you’ll have to put a hidden field in to make it loop on the same record. There are probably better ways that I don’t know about. Hope this helps.