Re: How to continue a line -- space_underscore

Hi, Crystal.

For me, it is also helpful here

If you're only posting for your own benefit, then please disregard my and
others' requests to accommodate the idiocyncracies of the medium you're
using. If, on the other hand, you think your posts include information that
may be of benefit to others, then please reconsider using best practices for
UseNet's medium, not for UtterAccess's medium.

it has become a habit -- hard to break those ... I had to stop myself from
doing it again ;)

Perhaps you don't use your newsreader this way, but one efficient method of
reading through the newsgroups is to _not_ use the "group by conversation"
mode, so that favorite posters can be spotted quickly, regardless of which
threads they reply to. Select a favorite poster's post in the window and
sort on subject -- and then one can read through the entire thread, except
for the posts where the author changed the subject. Those posts land
elsewhere in the sort.

I realize I almost never read your posts, yet I'm fairly certain you post
quite often. I suspect it's because you often filter yourself out of the
threads I read by changing the subject line. Perhaps you've written
something profound, or clever, or hilariously funny in your posts. I'll
never know . . . .

I've run out of time again. More later.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.


"'69 Camaro" <ForwardZERO_SPAM.To.69Camaro@xxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:OyxTfMMQHHA.4412@xxxxxxxxxxxxxxxxxxxxxxx
Hi, Crystal.

On UtterAccess, where I post the most, it is very helpful to specify more
complete information in the subject line.

UtterAccess isn't UseNet. While there are similarities between the two,
they're mostly apples and oranges.

UtterAccess is a Web-based application connected to a database on a Web
server, where folks can sign in as a member to add new child records
(i.e., post replies) to a chosen parent record (i.e., specific questions),
or to start a new parent record that they and others will add their own
child records. Even if one changes the subject line in the reply, that's
only one column of the record. The "subject line" column is not the
foreign key that references the parent record, so the child record (one's
posted reply) is still related to the parent record (the question posted),
no matter what one changes the subject to. When the records are
displayed, it's the parent record with all of its child records, and
there's no loss of child records when the value of that "subject line"
column is changed, even multiple times.

In contrast, Usenet is a worldwide network of thousands of news servers
which (mostly) don't require membership or subscription to post a file
(news article). These separate files are each given a message ID when
posted to a news server and then organized according to subject line and
referenced messages. Afterwards, the file is propogated throughout the
network to the other news servers. Some of these files get lost, so if
the only information the newsreader can use to organize the files into a
hierarchical thread is arbitrarily changed by the author, the author's
words may not be read by the intended audience because the news article
doesn't show up where the audience expected it to.

What one can get away with on UseNet won't always fly at UtterAccess.com,
and vice versa. The old adage, "When in Rome, do as the Romans," applies
here.

I've run out of time again. More later.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.


"'69 Camaro" <ForwardZERO_SPAM.To.69Camaro@xxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:OQFwGbLQHHA.4172@xxxxxxxxxxxxxxxxxxxxxxx
Hi, Crystal.

Someone told me not to change the subject line awhile back -- but they
failed to tell me why (or at least a reason I could understand) -- so I
have tried to keep the same beginning at least, and only modify the end.

Many search engines differentiate newsgroup posts by the subject line, so
your "arguments that you took out back" will be filtered out much of the
time. Which is as it should be, since you decided that that part of the
discussion wasn't germane to the main discussion of the thread by
purposely changing the subject line and branching off.

I use Thunderbird and everything stays linked.

If one uses Thunderbird to search through a decade of the newsgroup
archives, one likely won't see the problem of orphaned posts. If one
searches the decade-old archives without Thunderbird to any great extent,
this problem will bite one in the nose within a few days.

How prevalent is this problem?

Those who are using the two most popular newsreaders may see the problem.
The majority of posts to UseNet use these two newsreaders, so it's fairly
widespread.

Seems to me that a reader that can't keep the threads together should be
discarded for one that can...

Some newsreaders are better at it than others, but newsreaders keep the
posts in the threads together by checking the subject and the referenced
posts. Once the subject is changed mid-thread, it becomes a new thread
if the referenced posts aren't available, which occasionally happens. If
the subject doesn't change, the posts are usually kept within the same
thread, even if some of the referenced posts are missing. Since one
cannot guarantee that the posts replied to will stay in the archive, it's
best to keep the subject line intact, even if there are misspelled words
or one disagrees with the original poster's choice of subject.

I've run out of time. More later.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.


"strive4peace" <strive4peace2006@xxxxxxxxx> wrote in message
news:e1fewSHQHHA.320@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for explaining that, Gunny. Someone told me not to change the
subject line awhile back -- but they failed to tell me why (or at least
a reason I could understand) -- so I have tried to keep the same
beginning at least, and only modify the end. I use Thunderbird and
everything stays linked.

How prevalent is this problem? Seems to me that a reader that can't
keep the threads together should be discarded for one that can...

On UtterAccess, where I post the most, it is very helpful to specify
more complete information in the subject line. For me, it is also
helpful here... and it has become a habit -- hard to break those ... I
had to stop myself from doing it again ;)

I don't understand using the term "hijacking" ... why do you call it
that? I also don't understand using "commandeering" ... can you please
explain? thank you


Warm Regards,
Crystal
*
(: have an awesome day :)
*
MVP Access

strive4peace2006 at yahoo.com
*



'69 Camaro wrote:
Hi, Crystal.

Please don't hijack threads by changing the subject line. While many
newsreaders will keep posts in the thread intact regardless of the
subject, some newsreaders do not. In those newsreaders, once the
subject is changed, it starts a new thread in the middle of a
conversation, often leaving a confusing context for the reader to try
to sort out the trail of.

So by changing the subject, even to correct a spelling mistake, one
risks losing one's audience. One may also give the impression that
this part of the conversation shouldn't be handled within the original
conversation, as in "Let's take this fight outside so the others don't
get involved in our disagreement." And by commandeering the thread,
one also risks offending the original poster.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and
tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.


"strive4peace" <strive4peace2006@xxxxxxxxx> wrote in message
news:e5bnmQ9PHHA.4492@xxxxxxxxxxxxxxxxxxxxxxx
Hi Nancy,

if you are breaking a string, you will need & ... but if you are not,
then you won't.

Here are some examples:

'~~~~~~~~~~~~
strSQL = "SELECT email " _
& " FROM [YourTablename] " _
& " WHERE conditions " _
& " ORDER BY somefieldname;"
'~~~~~~~~~~~~

& is used because the SQL statement is one string

'~~~~~~~~~~~~
Msgbox "This is a message" _
, _
, "Here is the title"
'~~~~~~~~~~~~

& is NOT used here because the different lines are used just to make
the parameters easier to follow and there is nothing that needs to be
concatenated (combined)

... it just depends on what the statement is and where you break it

'~~~~~~~~~~~~
Msgbox "This line one of a message" _
& vbCrLf & " and line 2 of the message" _
& " because vbCrLf means to add a line break" _
, _
, "Here is the title"
'~~~~~~~~~~~~

when you do break lines, remember to add the necessary spaces! I like
to put & at the beginning of a line if it needs it as well as start
each literal string with a space if it is a continuation


Warm Regards,
Crystal
*
(: have an awesome day :)
*
MVP Access
Remote Programming and Training
strive4peace2006 at yahoo.com
*



Nancy wrote:
Thank you. Yes that is what I meant. I realized it wasn't very
detailed, so I did another post. Actually, the other response said &
_ (amersand, space, underscore)
I guess I will try bother.







.