Re: Links and attachments continued

[Goober Writer <gooberwriter -at- yahoo -dot- com>]

What's the context of the situation involving linking?

> Each module has a number of fields that can
> reference/link to/connect to
> one or more records in another module.

What are these "modules"? Database tables? If so,
there is specific terminology you should use so you
don't confuse people who might actually know about
database administration (even those who only know a
tiny bit).

> The user presses a button which
> opens the "linked" module, searches for the correct
> records and then
> presses an Add buton in the "linked module".  Then a
> link/connection is
> made and a brief summary/title of the record is
> pasted into the "linking"
> field in the source module.

The user action and what is happening in the
"background" should be tied together using common
terminology. It makes most sense to use the
appropriate terminology for the "background" for both
user action and expected result. This decreases the
likelihood for confusion and teaches the more clueless
users a thing about what's actually happening when
they click a button. Then, they are more likely to
understand what they are doing and be able to
communicate effectively to others about it when
needed, especially in times of trouble.

> I need the correct terminology to describe:
> 1.  The "source" module in which the link/connection
> is made.

Well, what is it? A database table? A CD? A bucket of
chum?

> 2.  The field in the source module in which the data
> from the
> linked/connected/referenced records are pasted.

Would most-likely be a column or row (or record) if
this is a database system you're talking about.

> 3.  The "target" module from which the records are
> linked/referenced.
> The correct direction of the
> linking/connecting/referencing needs to be
> clear to the user

Well, most database tables are connected via joins...

> 4.  A term that describes how the connection is made
> that also implies the
> direction of the linking, ie. the source module
> attaches to the target
> module, the target module ???attaches back to the
> source module.

outer join vs. inner join vs. natural join vs...

There's nothing wrong with using the correct
terminology and defining it.

> The concept of how the linking works is quite
> important for the user to understand.  

Then explain it using the proper terminology.

> The record that is linked/referenced
> can only be edited and
> saved when open in its own module.  

You lost me there.

> Any changes are automatically updated
> in any "linked" records.

Oh... sounds like an outer join by column to perform
attribution from one table to another... Why didn't
you say that in the first place? ;)

I don't mean to make light of you r post. My intent is
to show how using the proper terminology can help in
the understanding of the task.

=====
Goober Writer
(because life is too short to be inept)

"As soon as you hear the phrase "studies show",
immediately put a hand on your wallet and cover your groin."
      -- Geoff Hart

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

ANNOUNCING ROBOHELP STUDIO

RoboHelp Studio maximizes your Help authoring power by combining 
RoboHelp Office and RoboDemo, so you can easily create professional 
Help systems that feature interactive tutorials and demos.

Find out more about RoboHelp Studio at http://www.ehelp.com/techwr-l2

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.