What attracts you to threads?

[malik641]

Hey everybody!

Over the time of being here, I've noticed that I have been answering many more threads rather than starting new ones and asking questions. That's thanks to all of you for helping me out when I was just starting, and I appreciate that :). When I started out, I mostly looked at my own threads to see everyone's responses to my questions and previously answered threads trying to find an answer to a problem I had that I was sure was solved before (to note: About 90% of the time I spend here is in the Excel section). I had strayed away from threads I had no clue about or seemed too difficult for me. It's funny, because now I do the opposite. I still try to help out beginner questions, but the harder ones are what interest me more. About half of the time, I'll post back trying to help for a solution. The other half, I subscribe to the thread and watch it (hopefully) develop and get some answers.

So, I was wondering what posts you look at most. Beginner questions? Difficult questions? Other?

I voted Unanswered threads, because questions that have about 20 views and no answers interest me (given that the thread has a properly asked question). And I do like a good challenge.

I guess this poll will be time-specific. By that, I mean to say that the poll option you choose today may be different next year. But I'm just curious to see the results ;)


By the way: If anyone would like to suggest a modification to the poll options please be my guest. I wasn't sure if the options were all that good...

[mikerickson]

It varies with my mood.
If someone wants to find the last cell in a column (again, yes, I know its a new question to the poster)......it depends.

If someone appears to be learning, "How do I use arrays" posts rather than "I (my Boss) wants debits in blue, I don't care how" posts.

If it looks like a fun problem. Is there a recursive UDF in the solution or does the poster need help in sorting through a thicket of nested ifs?

[Steiner]

Depending on my mood I've three favorites:
- If I feel helpful (and I'm sure I've the time to come back) I pick topics I'm familiar with and try to help.
- If a topic I don't know much about sounds interesting, I have a look to learn something new.
- If I have really bad mood and look for entertainment, I watch some bashing at "URGENT!!!!"-threads.

Daniel

[Bob Phillips]

Great question Joseph!

Personally, I am attracted to quite a few types of question. Like you I am mainly Excel, because it is the only real development platform in the Office suite, but I do occasionally dabble in Word, PPT and Outlook (but hex on Access!)

My own favourite is tricky(ish) formulae questions. I like Excel formulae, and feel there is far too quick a propensity to reach for the VBA pen, so I always home in on these (and enjoy reading Shaz's alternatives as well).

Then there is the pure VBA problem, but where the guy is a regular, and you know that this is part of a journey for them, and you can help them. We all know these guys, AussieBear, YellowLabPro, colierville, moa when he was here, and even newer guys like anandbohra. These guys are clearly deeply into Excel and VBA, but they either don't have the background, or as much aptitude yet, and need assistance. Helping them is productive for them, and satisfying for us.

IT is also good to see people developing themselves. When Simon Lloyd joined us I would venture that he was a novice. Applying himself, he has moved on, helps more than he asks now, and is even a moderator on another forum. I think we have helped himn get there, and I always read his answers when I spot them.

I tend to read some of the more off-beat (to me) topics, but usually don't get involved in them, to see if there is anything of interest (found a great keyboard thanks to one-such by Malcolm). Things like questions about OS's, other technologies, etc. I like Stanl's posts, they are always interesting, but the poor guy rarely gets any help here. I even followed Cosmos' recent posts about computer chairs!

Personally, I drop out of threads when they start getting long, and the number of participants increases. I feel these usually go off-thread, or there are so many differeing views, it is hard to follow, and hard to give the OP time and space to get his views/thoughts in.

And of course, the OT topics. Often something good there where we can wade in with our prejudices, our hobby horses, and just sound off.

Time to start a thread - if I could just think of a topic.

[mvidas]

My steps of answering a question (or attempting)
1) Replies: 0 (or replies: 1 where the only reply is the OP asking "anyone?")
2) Question isn't something like, as mike says, finding the last cell in a column. I generally try and leave those for the people on their own vba journey and can get the satisfaction of answering a question
3) OP not on my personal avoid list (few but existant)

I read most all non-question threads except for the introductions (generally)

[matthewspatrick]

I tend to skip the questions that already have several posts, mainly because it can be too time-consuming to catch up on what has already been written and figure out something new to offer.

That said, if I see a question on a subject that intrigues me for one reason or another, I will read it, even if I do not post to it.

Now, to pick on Bob a little for some off-topic action... :devil2:



Personally, I am attracted to quite a few types of question. Like you I am mainly Excel, because it is the only real development platform in the Office suite, but I do occasionally dabble in Word, PPT and Outlook (but hex on Access!)

Access gets a lot of abuse from some quarters, and honestly I cannot understand why. Yes, it is not suited for mission-critical applications, or apps where security or web enablement is high priority. That said, Access does offer a relatively simple RAD platform for those willing to accept the limitations. I've seen some marvelous work done in Access, and some crappy work done in Access; it's not Access that makes the final app marvelous or crappy, but the choices made by the developer.


My own favourite is tricky(ish) formulae questions. I like Excel formulae, and feel there is far too quick a propensity to reach for the VBA pen, so I always home in on these (and enjoy reading Shaz's alternatives as well).

I tend to agree; I prefer to "go native" with Excel functions instead of UDFs. They are much faster, and any time you reach for VBA you have the potential problem of people not knowing how to add it to the project and/or enable macros. However, there are times when I will go the UDF route to avoid a hideously complex formula. My basic test: if I think I would have a hard time understanding a formula if I had to come back and edit it a year from now, then it may be worthwhile to take the performance hit and write the UDF.

[Bob Phillips]

Now, to pick on Bob a little for some off-topic action... :devil2:

You want some action, you got it <G>.


Access gets a lot of abuse from some quarters, and honestly I cannot understand why. Yes, it is not suited for mission-critical applications, or apps where security or web enablement is high priority. That said, Access does offer a relatively simple RAD platform for those willing to accept the limitations. I've seen some marvelous work done in Access, and some crappy work done in Access; it's not Access that makes the final app marvelous or crappy, but the choices made by the developer.

I am sorry, but you will NEVER convince me that Access is a useful RAD platform. I agree it is the only competitor to Excel in the Office suite, but it is so far behind as to make it a meaningless race.

There is nothing I can do in Access that I can't do as well or better in Excel, but the same cannot be said about the obverse. I use Access as a datastore, because it is sometimes simpler, and if my client insists, otherwise I use Excel, Excel and SQL Server, Excel and Sybase.

But you are right, the tool doesn't make crap applications, designers and developers do.


I tend to agree; I prefer to "go native" with Excel functions instead of UDFs. They are much faster, and any time you reach for VBA you have the potential problem of people not knowing how to add it to the project and/or enable macros. However, there are times when I will go the UDF route to avoid a hideously complex formula. My basic test: if I think I would have a hard time understanding a formula if I had to come back and edit it a year from now, then it may be worthwhile to take the performance hit and write the UDF.

I agree with all of that, but my comment was with regard to answering questions. Only today a guy wanted a UDF to count unqiqu instances in a range. He quoted a web page that showed him a SUMPRODUCT function that did just that, so why create a UDF? And worst of all, he got a reply giving a UDF that invoked COUNTIF, noything more!

[Brandtrock]

I will go to questions that interest me in the areas that I feel most confident in.

The unanswered questions that have been viewed several times usually get a view by me. I'll try to provide an answer or at least a hint in the right direction if the question is written clearly.

Regards,

[moa]

Occaisionally I look at threads that have some well known (to me) name attached and are of interest, or could possibly be of interest, to my project. Not that I have an Excel project at the moment.

Some of the board regulars always have some really useful code or formulae to share and a couple are good for verbal fisticuffs once in a while. I'm naming no names... but xld fits both those categories.

[malik641]

Then there is the pure VBA problem, but where the guy is a regular, and you know that this is part of a journey for them, and you can help them. We all know these guys, AussieBear, YellowLabPro, colierville, moa when he was here, and even newer guys like anandbohra. These guys are clearly deeply into Excel and VBA, but they either don't have the background, or as much aptitude yet, and need assistance. Helping them is productive for them, and satisfying for us. Couldn't agree more. These are the kind of people I like to help, because you know that they will take the knowledge you give them and do something useful/productive with it.


IT is also good to see people developing themselves. When Simon Lloyd joined us I would venture that he was a novice. Applying himself, he has moved on, helps more than he asks now, and is even a moderator on another forum. I think we have helped himn get there, and I always read his answers when I spot them. I do the same for rory, richard school, oorang, to name a few. And I've always liked Erdinc's questions. They always seem to be so different than most questions.


(found a great keyboard thanks to one-such by Malcolm) Did you ever buy that? If so, how do you like it?


I like Stanl's posts, they are always interesting, but the poor guy rarely gets any help here. Me too. I try to help out whenever I can with him, even if I have NO clue about the subject. For somebody who doesn't get many answers, he sure sticks around. And for that effort, I will give mine.

[TrippyTom]

This topic's number of responses has become too large for me to pay attention to.


JUST KIDDING! :rotlaugh:

1) As said before, anything that has "Please help -- need asap!" is ignored straight away by me.
2) Anything that sounds like a homework question I usually reply to with disdain.
3) I normally pay more attention to the PowerPoint section of this site, as I do more in that than the other programs in Office. I do peek at the clever solutions in the Outlook sometimes too.

[Ken Puls]

There are a few things that will draw me in to a post:
-Topic. I pick ones that sound interesting mostly, and don't tend to bother with the ones that look really easy as much any more.
-Authors/contributors. There are certain posters who I've helped in the past (Simon Lloyd is an example,) whose posts I'll try to look in to. The other side is that if I see a reply by certain people I'll drop in for a peek. (Bob's posts are usually worth reading. ;) )
-Number of replies. I tend to like answering ones with no replies yet, or a very low count. As has been said before, it just takes too much time to catch up later if the thread is long on its way. (That can be trumped by the subject, and if I see someone like Bob still there after 20 posts. <g>)

[Tommy]

It depends on how much "free" time I have, if I can't come abck and follow up I will not post even if out of curiosity I developed a solution. I also tend to post VBA answers/solutions . :doh:

So far as the topics of the post, I skip "URGET", I laugh at "Help Please" and look and move on. Otherwise if it's not to crowded I look and see if I am interested. But for the most part I look at questions that are in the area I am in at that particular time. If I am working with a solution that works with Excel I look into excel related Q's, or Word, or Access, or Acad... if I use a database I prefer PostgreSQL.

The question I wiil look at every time and not respond is "How do you " do something with a batch file. I don't know but I always look until the answer is resolved. Some of these answers are more criptic than reg expresions!! No help file, no nothing, you either know or have enough knowledge to figure it out.

I have worked some questions for months (2 1/2 is the record for me anyway LOL). I just enjoy helping, I was assigned a task with no help and didn't like the feeling. So I try to help where ever and when ever I can.

[XLGibbs]

I prefer the 0 replies and many views in Excel or Access. I check out almost any thread with more than 3 pages because it is either a great topic, or it ends up being great entertainment.

Things to avoid:
"Please help ASAP" or variations are usually read, but also avoided.

I look forward to helping someone solve a problem, but not entirely doing the work for them.

I agree with XLD. I avoid Access like the plague, but know enough to help out occassionaly (or attempt to learn something) in the Access forum. I generally do excel with SQL solutions unless Access is specifically requested. Incidentally, in most cases when Access is requested, it is because they have no knowledge and think that is the only possible tool for the job. Once I explain that excel can do more for them as a solution, they are fine with not using excel.

Unfortunately, 90% of my time is in SQL and C#, and I am up to about 80 hrs per week for work. SO the rare instances I do get to stop by, almost everything is "handled". SHould be around much more in the fall/winter though, it was an unusual summer for work.

[malik641]

Unfortunately, 90% of my time is in SQL and C#, and I am up to about 80 hrs per week for work. SO the rare instances I do get to stop by, almost everything is "handled". SHould be around much more in the fall/winter though, it was an unusual summer for work.
I wish we had more SQL-type problems/solutions. Actually, I really wish we had a SQL section (I am starting to really get into SQL) on the forum...but I believe it is out of the scope of this forum (not because of the posters, but rather the fact that this is a VBA forum....).

....maybe I could start another section on SQL.....:think:

[Bob Phillips]

You could. Make it SQL Server rather than SQL, and VBA is a natural conduit.

[XLGibbs]

I wish we had more SQL-type problems/solutions. Actually, I really wish we had a SQL section (I am starting to really get into SQL) on the forum...but I believe it is out of the scope of this forum (not because of the posters, but rather the fact that this is a VBA forum....).

....maybe I could start another section on SQL.....:think:

I wanted that a long time ago when I started here. I would be all for it. VBA and VB solutions and excel go hand in hand--at least in my world they do.

[Sir Babydum GBE]

OMG - Nobody like's my threads!!!

That's it - I resign.

[malik641]

OMG - Nobody like's my threads!!!

That's it - I resign. :rotlaugh::rotlaugh::rotlaugh::rotlaugh:
You are TOO funny Sir Babydum!



You could. Make it SQL Server rather than SQL, and VBA is a natural conduit.
I wanted that a long time ago when I started here. I would be all for it. VBA and VB solutions and excel go hand in hand--at least in my world they do.
Sounds like a plan to me. SQL Server it is. I'll place the post for the new forum.

[malik641]

Ok, forum requested here (http://vbaexpress.com/forum/showpost.php?p=111876&postcount=45).

[malik641]

And the SQL forum EXISTS (Here (http://vbaexpress.com/forum/forumdisplay.php?f=94)). :) :clap:

This is totally gonna be my new hang out spot :yes

[malik641]

Wow. There are more people viewing the empty SQL forum than some of the other forums!

[Charlize]

Wow. There are more people viewing the empty SQL forum than some of the other forums!I thought it would be an interesting link that you have given in your previous post.

[geekgirlau]

I am sorry, but you will NEVER convince me that Access is a useful RAD platform.

Actually I love Access as RAD, with the proviso that SQL Server is the backend. You get to create a quick, distributable user interface with the security and processing speed of SQL for data handling.

[geekgirlau]

I am sorry, but you will NEVER convince me that Access is a useful RAD platform.

Actually I love Access for RAD, with the proviso that SQL Server is the backend. You get to create a quick, distributable user interface with the security and processing speed of SQL for data handling.

[malik641]

I thought it would be an interesting link that you have given in your previous post.
Sorry, at the time I posted it was an empty forum. I was just directing everyone where it is located. It has one thread now...so it is starting to get interesting :)

[YellowLabPro]

The Girls......

[malik641]

The Girls...... Figures :devil2:

[Zack Barresse]

The Girls......

ROFL! :rotlaugh:

Would you believe me if I said the bribes? :whistle: