On-Click Events and motion tablet signature boxes?

[ELeigh]

I have a fairly involved form with 54 option frames. Each frame has 4 option
buttons (IN, OUT, N/A, N/O). I already have the option frames setup to
update their status in a table with numbers (1,2,3,4) and all this is linked
to a specific record number that is auto generated. I can create multiple
records that retain my choices for all 54 option frames.

What I want to do now is create a table with a list of pre-written comments
and an event on each option frame so if I select OUT it will select a
specific comment for that specific option. I might select OUT on the option
frame for line 1, line 5 and line 25. The rest of the lines might be IN, N/A
or N/O. Those won't matter for this purpose. I need it to select comments
specific for those OUT lines and place the comments in some field that will
print out on my form. I will probably even need to create a pop-up list box
that allows for the choice from a selection of comments for a specific line.

I have figured out how to create a calculated querry with an if/then
statement that will print a specific message in a text box when that option
reports a 2(OUT) but I'm not sure how to make it append another selection to
the original. If that is even the best way to go about coding this. I was
thinking that perhaps an on-click event would be the way to go.

I have what I would call a motion tablet. The entire face is a writting
pad. I'm wondering if I might be able to create a signature field on my
form, in access of course, so a person could sign it on the computer, like
the UPS delivery guys, lol. The computer has a writing field but it attempts
to convert your writting into text when you select insert. I haven't found
an option yet that would just allow me to insert the real writing.

I'm an access noob and trying to teach myself how to make this form but this
problem is stumping me. If it's something you can explain yourself great if
this is explained elsewhere and you can direct me to it then that's great
also. Thanks in advance for the help.

 

[ELeigh]

Thought I would mention this is with Access 2003 SP3. Thanks!

 

[Tom Wickerath]

Hi ELeigh,

I have a fairly involved form with 54 option frames.

This is going to require 54 fields in the table. Such a design in most
likely not a normalized design, but rather an "Access spreadsheet". My guess
is that you have a "many-to-many" (abbreviated M:N) relationship between each
record and the attribute described by each option frame. A properly
normalized database requires a minimum of three tables to model a M:N
relationship. This is accomplished by defining two "one-to-many" (abbreviated
1:M) relationships between each "parent" table and a common intersection
table. Other terms for an intersection table include a join or linking table.
This join table needs to have the foreign keys of both 1:M relationships.

Starting with a proper design will make all your future work MUCH easier. A
design that requires you to add or remove fields, in order to accomodate new
choices [or remove existing choices] should immediately raise a red flag in
your mind. Commit the following phrase to memory:

Fields are expensive
Records are cheap

In other words, you design should be such that it allows you to add or
remove choices that you are currently making with the 54 dedicated option
frames simply by adding or removing records from table(s). With that
preamble, I'd like to suggest that now is the time to immerse yourself in
database normalization. Start with this link, and make sure to read the first
two articles by Michael Hernandez:

http://www.accessmvp.com/JConrad/accessjunkie/resources.html#DatabaseDesign101

Good Luck!


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
__________________________________________