Stuart,

the problem is, it is not easy to say what it is important to describe or
not,
sometimes you just do not see it. It happens to us a lot of times. You
describe
something that for you is perfectly clear and receive blank looks and
"what..?"
And even when the description of the problem is very detailed, there still
can
be more than one possible cause. This is the fun part of our job. I really
do
not see why you are so annoyed to give more than one answer, and I do not
find
it a waste of time. We learn a lot from each other, and the more we post the
more we learn.

I do not want to raise an issue here, it is just a thought... I am *much*
more
annoyed by posts that deserve a RTFM, and even in those cases I just delete
the 
email.

Cheers,
Marco

-----Original Message-----
From: Stuart.frost [mailto:stuart.frost@n...]
Sent: Tuesday, July 30, 2002 2:29 PM
To: professional vb
Subject: [pro_vb] Re: datagrid-vb6


Everybody who reads these newgroups (and the few of us making the responses
;) )
must be fed up of really vague questions by now.

EVERYONE needs to SPECIFY AS MUCH ABOUT THE PROBLEM AS THEY CAN or else why
should we waste time trying to give five or six possible answers for which a
minimum four or five
must logically be incorrect solutions?

For the last time:

1> When you've done changing the field have you used the RecordSet.Update
method?
2> Use an ADO command to perform the update: Command.CommandText="UPDATE
MyTable SET UpdatableValue = 'Sidney' WHERE itsID=1" then Command.Execute
numberOfAffectedRows to execute it.
3> If your database supports row level locking, you might not have access to
modify certain rows.


This really is the last time I'm giving more than one answer. Please try to
be specific from now on.

Best of luck anyway.

Stuart Frost
stuart.frost@n...