attachments

  • Thread starter Thread starter JohnE
  • Start date Start date
J

JohnE

Hello. I have a dillemma and I'm not seeing the way to work it so I seek the
thoughts of the group. I need to allow for attachments to a project, the
project version, the project version task, any task notes, and so on. What I
thought of doing is having one table (tblAttachment) that stores all the
pathways, descriptions, etc to the attachments with set of checkboxes as to
what the attachment pertains to. This would be bound to a continuous form.
Here is my dilemma. A scenario would be; an attachment is for the overall
project. I would do the pathway and check the project checkbox. The
attachment form would be linked to the main form listing the project. This
shouldn't be a problem. The scenario I am having difficulty getting my mind
around is if the attachment relates to a task note only. On the form I do
the pathway and check the task note checkbox. How will it know which task
note the attachment goes with?

I've tried working this several different ways sofar but run into a road
block. I am open to suggestions on how to proceed with this or if anyone
knows of any samples/examples I am able to review, either would be
appreciated.

Thanks in advance for any assistance.
.... John
 
John,
In tblAttachment you need a field to store the ID of the project record.
So each time you move to a new project, the tblAttachment can select all the
attachments for that particular project.
This is a one to many relationship between projects and attachments.
You may want an fields in tblAttachment to store the type of field the
attachment if for eg Notes, contract etc.
Avoid have lots of checkboxes by having a drop down box with a list of what
type of document the attachment is.


Jeanette Cunningham -- Melbourne Victoria Australia
 
Jeanette, thanks for the info. Another concern I have (and again, I could be
thinking about this too much) is if the one attachment pertains to more then
one item (ie; task and version)? Which is what I was thinking about with the
checkboxes. But, I agree with you about avoiding checkboxes, or limiting
their use. Thanks for your feedback. It has given me another thought on
doing the attachment which I will try tomorrow at work. Let me know if you
have other thoughts on this.
Thanks ... John
 
If the task applies to more than one task or version, I would just attach
the attachment again
- unless this will happen frequently.
If it happens frequently you can create a 3rd table that stores just the
ProjectID and the AttachmentID. This table is related one to many to
tblProjects and one to many to tblAttachments.


Jeanette Cunningham -- Melbourne Victoria Australia
 
Jeanette, that is along the lines that I was thinking of. From your prior
reply it gave me the idea of having 2 comboboxes. One would be the type
(task, note, etc) and the second would fill with what is selected in the
first. Thus giving me which task, note, etc the attachment is for. If the
attachment applies to more then one item, list the others the same way.
Thanks for helping me get my mind around this.
.... John
 
Back
Top