Comments Field

[RussOSU]

I have created a database which will be used to track job requests. I have all the fields except for a comments field created. I am curious what the best way of creating this field would be. Would it be best to keep this as a seperate table as to allow for multiple instances connected to one request or should I include the field with my request table? I know this is all really an individual prefernce type decision but I am curious to what would/ has worked best for others.

Thanks
Russ

 

[JoeMiller]

It really depends on whether you need to maintain history on the notes. For instance, if you make a note today, then change the note tomorrow. Would you ever want to go back and view the first note you made? If yes then I would suggest going to the separate table. A memo field in the main table would work fine in this respect to if you have people put their comments always at the top or always at the bottom, but you have more control if you make a separate table and then put a date stamp everytime a memo is made. You are correct in that it's more of a personal preference than a design issue.

HTH Joe Miller
joe.miller@flotech.net

 

[PamelaG]

Hi Russ!

My two cents on the issue, which is a common one, is that you never know what you will want to do in the future. Print out a list of the most recent comments? Add a comment author field? The linked table solution leaves you more options in the future without having to copy your data into a new table after the fact. I always go for the solution that leads to an open door as opposed to a dead end if possible.

And just remember that you have limited functionality on Memo data type fields. Don't end up collecting data in there that you might want to put into a combo box or query on!

Pamela

http://www.accessinsight.com