Julynn Posted December 12, 2008 Posted December 12, 2008 I'm developing a simple project management database. Each Project has a tab for Related Project Files. I've created multiple container fields for the files and would like to associate a time stamp with each file/container field. However, my time stamp fields all reflect the same time even though each field is uniquely named. I'm guessing I can only have one time stamp field per record?? Is there a better way to accomplish my objective?
bcooney Posted December 13, 2008 Posted December 13, 2008 Welcome! If you don't mind, I'd like to confirm your structure. I would have a Project table and a related table of files (related by ProjectID). This table would need a container field to store the file, a modified timestamp if you want, and a primary keyID field (perhaps also a note/comment field). I'd show the related files in a portal on the Project Form layout.
Julynn Posted December 15, 2008 Author Posted December 15, 2008 Thanks for your reply. However, either I'm not understanding your suggestions or we're not on the same page in terms of what I am attempting to accomplish. Since a picture is sometimes worth a thousand words, I've uploaded a screenshot of my Project Form layout. Within that layout is a section for the Tasks related to a Project. Within the Tasks section are 3 tabs. One of the tabs is for storage of related files such as Word documents, Excel spreadsheets, etc. Within that tab, I am trying to create a way to store related support documentation and show the modification date for each file. [color:red]I guess what I'm really trying to do is attach a modification date to each container field. (I had created 8 unique container fields. e.g field1, field2, field3.) Can I do that or does each support document need to be entered into its own record? In which case, your suggestion of a primary keyID field makes more sense.
bcooney Posted December 15, 2008 Posted December 15, 2008 (I had created 8 unique container fields. e.g field1, field2, field3.) Can I do that or does each support document need to be entered into its own record? In which case, your suggestion of a primary keyID field makes more sense. Yes, this tab needs to show a portal to related records in a DOC table. The Doc record has the modification ts. The DOC record would have a _kF_ProjectID.
Recommended Posts
This topic is 5822 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now