You can do this:
With objMailItem
.To = "EMAIL ADDRESS HERE"
.Subject = "Site Inspection for " & [Area] & "At " & [Date]
.Body = "Some text here"
if isnull(rstAttachment.Fields("Filename")) = false then
.Attachments.Add (strAttachementPath)
End if
.Display
End With
I used Cdo to strip the attachment from the email and save the email to
A share drive. I then placed the path in an attachments table. No too
Smooth, but effect
With that in mind you can have the charatoristics table that houses what the detail is about (project, AMS, IP) and the description, and still ink that to the Project table.
CharID (PK)
ProecjtID (FK)
CharTYpe (Project, AMS, IP, IF)
Char Description
you had the recordsource of the form tied to the value in the combo box. When a value was selected, it showed that 1 record. I placed a show all button on the form for you to redefine the forms dataset.
In a normalized database this can be accomplished in a listbox that is requeried.
So everything start at the product. Lets start there. Lets start to redefine the data a bit, how about "Charactoristics"? So we have a charactoristics table. THe Charactoristics of the Product are FLEX, AMS...
I believe that the combo box in question is filtering the form. If you are in Access 2007, then the "Filtered" down at the bottom glows orange. You can toggle that by pressing the "Filtered" button on the navigation bar.
I agree with boblarson. We need some details about the process and what you are tracking. Looking that the AMS_IP_Table table the data in the IP Iniside AMS IP violates the first normal form. To be in 1NF, each column must contain only a single value and each row must contain the same...
I created a student table and joined it to the Craft table. Did you look at the normalization article? Attached is the update. I would also look up relationships in help to guide you in the database design.
When looking at the tables, ask yourself, "is the data in the Students table ONLY...
You can then drag that table into the QBE 2 times and Outer Join the Parent to the PersonID to get all relavent information. Allen Browne has a great explaination here:
http://allenbrowne.com/ser-06.html