Q?

KenHigg

Registered User
Local time
Yesterday, 22:55
Joined
Jun 9, 2004
Messages
13,327
Is it ok to just bail out of a thread where you've been trying to help somebody with an issue when you seem to be making no progress because the other user has no clue of how to do even the most basic things in Access?
 
In a word, yes.

That is to say, if you've gone as far as you can with someone, I think it's fine to say that you're sorry but you can't help any further and to leave it there. You've already tried your best to help.

Do I think it's rude to just stop responding, with no explanation? Yes.

On a similar note, I also think it's ignorant for people who've had help not to at least post back and say that the problem has been resolved (but I know there was another thread on that subject).
 
Is it ok to just bail out of a thread where you've been trying to help somebody with an issue when you seem to be making no progress because the other user has no clue of how to do even the most basic things in Access?

I have a feeling I have seen the thread and it is bail out time:)
 
I get fed up when the poster wants me to hold their hand through every little issue. they never even try but ask eg "Does it go round the statement?" I want to scream "well try the bloody thing"

There is a poster on at the moment and I'm sure Rural guy is writing his whole project bit by bit.

Brian
 
Last edited:
I've had a couple of occasions where I've had to quit on a thread, or at least threaten to in order to restore some sense of reason, where a poster's expectations and aims exceed their ability to comprehend the issues involved. In which case, I see nothing wrong with bailing out politely. I usually feel pretty bad at the time but, they're not paying for the advice or your time so oyu're under no obligation to them. In my opinion though, good manners dictates you should make some statement as to the fact that you're withdrawing from the thread.
 
In a recent post from Bob Larson he suggested there should be some effort from the OP and less spoonfeeding. People don't learn if they are just given a solution without understanding why it works. I just saw a post today when the OP wanted an explanation of the NZ function. Haven't they heard of Access Help.

It is also irritating when people reject sensible solutions from people here on the grounds that it is not exactly what they asked for even when that was plainly not good practice.
 
It is also irritating when people reject sensible solutions from people here on the grounds that it is not exactly what they asked for even when that was plainly not good practice.

I agree but I think the problem is often that people have a fixed idea of what they think they want, even if technically it's wrong. As someone who's travelled with this forum from total beginner to having some understanding of databasing I know there have been times when the outcome was far more important to me than finesse in method.

It can be quite a leap too (it certainly was for me) to understand what was written so often - that you need to get your design right at the start, not begin with something flawed then try to fix it later. To be fair I've got some fairly nifty databases working now but there are still times when I need a bit of spoon feeding when I can't see the logic and I suspect a lot of requesters are having difficulty wrestling with what seems arcane thinking rather than just being lazy.

The one thing I picked up on early here was use the search function and try to sort it yourself first before asking the question. It really is the way to learn.
 
I say yes. If they want advice that leads to a conclusion, then they can pay for it. Free advice here is a give or take thing (mostly take, the way some go on) but you have no obligation to help or to continue helping, lost cause or not.
 
Is it ok to just bail out of a thread where you've been trying to help somebody with an issue when you seem to be making no progress because the other user has no clue of how to do even the most basic things in Access?

I think it is fair to pull the plug when the thread turns from the sense of being helpful and starts to become either an unpaid project or a full fledged Access education. You get the same compensation for your efforts here for the whole answer or leading people in the right direction or not answering at all.
I am extremely grateful for people giving me answers or direction when I am stuck. But by no means am I hoping to get an A-Z education in database design, construction, implimentation and maintenance, such expectation would be entirely unreasonable to place upon someone who has the knowledge and in the long run would not help anyone out including myself.
Perhaps the best way to terminate a thread would be to mention that you can not offer any more help on the specific database and either offer to produce the work for the person on the side as a properly compensated task or direct the person towards a source of formal training and education. Just do it nicely because it might be someone who really does not get it and is not just playing dumb dumb to get the work done by someone else.
 
Last edited:

Users who are viewing this thread

Back
Top Bottom