Hi dragan,

>>Also, lets say, that I could save two hours of work with one thing out a VFP book. What about the time I need to read the entire book ? What about the time to order that book (I'm not even sure I can order them in such way that they are delivered at my door). And what to if I need some particular information RIGHT NOW ? I can't wait two or three weeks for a book to arrive; I NEED MY INFO RIGHT NOW.
>>
>>This for me are very practical reasons.
>
>Which have a very practical solution. The book is an investment in the future. If you need a ten second solution, hit F1 and find what you need there. That's not something you do with a book.

>Read it at your time, skim and just get a general idea of what's inside. Then when you need something, you will be able to find it fast. Or, if you have an eBook, even faster. You just need to know what's inside.


I think I agree, books are good for giving you general ideas of how to construct applications, best practises etc, In their hardcopy form they're less practical for small technical problems and/or HOWTO questions.

And I think that is my point. I really don't care what the books are saying about OOP, best practises design patterns etc. I've got my way of working which may or may not be in line of what the books tell me. There are enough articles on the Wiki, UT or MSDN telling me that either.

Walter,