Answering questions is how you become an expert. You do not become an expert by always having your questions answered by others or by having personal assistance "on call."
You do not need personal assistance. Personal assistance is nice if you want to learn how to do something quickly. An experts strives to understands what (s)he is working with so (s)he can address any question (by anybody, including yourself) that comes up. An analogy would be learning a physics formula to apply to some problem by heart versus understanding the physics and being able to reproduce the formula at will without every committing it to memory.
While having a (very specific) question answered on a forum can help you get unstuck, if you want to become an expert, you really should learn how to become self-reliant: you get your queries answered by: you. When a question pops up, you answer it by delving deeper. For example with your Crystal Reports: delving deeper means not only studying examples using Crystal Reports, but studying the Crystal Reports library code itself. That is how you start really understanding what the Crystal Reports library is about, how it is put together and thus how you can best put it to work for you and whether it is or is not suited to whatever problem you are trying to solve with it, and even how you could extend it to make it do what it can't at the moment...
Delving deeper is something most "production programmers" don't do. Go to any forum, including StackOverflow, and you will find that the community is largely divided into three groups:
- a majority of "askers": people who want help solving the problems they encounter. They do answer question as well, but looking at their StackOverflow profile you will see that their number of questions far outweighs the number of their answers.
- a minitory of "answerers": people who have encountered problems, solved them (with or without outside help) and are willing to help others. They do ask questions, but their number of answers far outweighs the number of their questions.
- a group (varying in numbers) of "askers" seeking to become "answerers".
So, if you want to become an expert at something: start answering questions. Your own questions as well as questions posed by others. If you don't know the answer to a question of the top of your head: do the research. If the answer has already been given, or you find it somewhere: make sure you do not "just apply" it (like copy-pasting the code), but that you understand why the answer solves the problem and what you would need to do if the question (the requirement) were slightly different.
Oh and the reason it is hard to keep an expert engaged? All answerers on forums are volunteers. Getting follow-up questions that make it clear that the asker is not taking the answer and running with it him/herself, is not very enjoyable and motivation to keep answering flies out of the window. Getting follow-up questions that show the asker has taken the answer and done some experimenting/research to further his/her understanding on the other hand is very rewarding. It may be advisable not to do this in the same thread, or on StackOverflow in the comments, but to start another thread/question where you show where you have taken the answer to a previous question, what you have tried and where you are stuck now.