By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,665 Members | 1,406 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,665 IT Pros & Developers. It's quick & easy.

Problem with forms

P: n/a
I have a table which is to hold 70 memo fields to contain notes on data
changes to corresponding fields in a form. The problem is I dont want to
have to create 70 forms to input notes into.
Is it possible to have one form that somehow opens up the correct notes
field to input the notes. I was thinking along the lines of having a button
against each line of data which then opened this form.
Below is the form layout with the notes field possibly being a link to the
notes entry form.

project1 date1 date 2 date3 notes
project2 date1 date 2 date3 notes
project3 date1 date 2 date3 notes
project4 date1 date 2 date3 notes

etc
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a

"David" <wi**********@yahoo.co.ik> schreef in bericht news:d8**********@nwrdmz02.dmz.ncs.ea.ibs-infra.bt.com...
I have a table which is to hold 70 memo fields to contain notes on data
changes to corresponding fields in a form. The problem is I dont want to
have to create 70 forms to input notes into.
Is it possible to have one form that somehow opens up the correct notes
field to input the notes. I was thinking along the lines of having a button
against each line of data which then opened this form.
Below is the form layout with the notes field possibly being a link to the
notes entry form.

project1 date1 date 2 date3 notes
project2 date1 date 2 date3 notes
project3 date1 date 2 date3 notes
project4 date1 date 2 date3 notes

etc


If you have 70 memo fields in a table, IMO you should reconsider your design.
You are doing a better job with 70 records in a TblMemo I guess.
If there is only *one* memo for each project, than you might put the memo field in the same table where you store your projects.
In any case: only use ONE form to edit the memo.
Open the form with a where-clause (or a filter)
like: Docmd.Openform "FrmMemo", , , "MemoID = Me!ProjectID"

HTH
Arno R
Nov 13 '05 #2

P: n/a
It looks like you are looking for a generalized comment that
you can attach to multiple fields. I agree with Arno's
suggestion that you have a separate table for those
comments. It could look someting like this:

Table: tblEditComments
MemoPK (Autonumber)
TableID (Text: The name of the table containing the data)
RecID (The format and values of your record Primary Key)
FieldID (Text: The name of the field you are commenting)
FieldVal (Text: snapshot of current/previous values for
context)
CommentText (Memo)
CommentDate (Date/Time: automatic date/time stamp)

1. I'm assuming that you are not using composite primary
keys.
2. I realize that by encoding the names of tables and
fields, there is a danger of getting out of sync when
renaming those entities.

To Arno's form suggestion, I would add that you look at the
OpenArgs argument, to give the form some context of the data
you are trying to comment. I'm guessing that you would want
to make the previous comments read-only, yet still have the
ability to add new comments.

Good luck!
--
Kevin Nechodom
University of Utah Hospital and Clinics
Kevin dit Nechodom ack hsc dit utah dit edu
"Call me paranoid, but I think you are reading what I'm
writing!"
Arno R<ar***********@tiscali.nl> 6/12/2005 4:38 AM >>>

"David" <wi**********@yahoo.co.ik> schreef in bericht
news:d8**********@nwrdmz02.dmz.ncs.ea.ibs-infra.bt.com...
I have a table which is to hold 70 memo fields to contain

notes on data
changes to corresponding fields in a form. The problem

isI dont want to
have to create 70 forms to input notes into.
Is it possible to have one form that somehow opens up

the correct notes
field to input the notes. I was thinking along the lines

of having a button
against each line of data which then opened this form.
Below is the form layout with the notes field possibly

being a link to the
notes entry form.

project1 date1 date 2 date3 notes
project2 date1 date 2 date3 notes
project3 date1 date 2 date3 notes
project4 date1 date 2 date3 notes

etc


If you have 70 memo fields in a table, IMO you should
reconsider your design.
You are doing a better job with 70 records in a TblMemo I
guess.
If there is only *one* memo for each project, than you
might put the memo field in the same table where you store
your projects.
In any case: only use ONE form to edit the memo.
Open the form with a where-clause (or a filter)
like: Docmd.Openform "FrmMemo", , , "MemoID =
Me!ProjectID"

HTH
Arno R

Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.