As I refered to earlier, the books mentioned in the other thread on Steve Macguire's book, Steve McConnell was mentioed too, give good idea's. Others have been mentioned, there are many good books & magazines available, Ed has obviously read many books on the subject, maybe he could be of help (gesture of friendship, there, trying to make up for any hard feelings - I know he's good at what he does & does deserves to be listened to, regardless of what he thinks my views of him are).

Don't concentrate on books for VFP, look for general books on programming. Jon Bentley's Programming Pearl's books give good tips on good practice (& quite a few horror stories too).

One of the best ways of learning is sharing your code & not being personnally offended by any reasonable criticism (no dig at Ed, intended, honest). Everybody here is willing to help, I have yet to come across anybody who is critical for the sake of it. But no one persons ideas are necessarily right, listen to everyone & learn from everyone & decide what works best for yourself. And learn to look critically at your own code, do you believe it could be done better. 1-2, 3, 12 months down the line do you understand your own comments. Can you see how your code could have been improved. Be your own worst critic. But read lots of books on technique, taking what works for you from each.

I'm no expert, & I do not make myself out to be one, I am learning every step of the way. I believe myself to be good in my own field (& my clients keep paying for more, at least one good sign), but I can see how I can be better & I always strive to do so.

Re-reading that reply, it sounds a load of pretentious crap, & probably is. But I think I'm passing on the sort of thing to try for.

Paul

>Paul,
>
>>But my view is commenting is an essential part of coding, it should be done at the time of coding & fully. It shouldn't be a brief reminder to yourself, that you will expand at some later date, because the time never arises, it will always remain as a brief cryptic reminder, that some other person will have to decipher at a later date.
>
>Since, I'm self employed and working alone, commenting my code has alway's been a pitty. Just recently I began to see that writing good readable code with good comments is paying off, particular in situations where someone else might use/see or analize your code.
>
>Unfortunately, I still haven't not found the proper way to make my code as readable as i like to. Can you give us some tips that might push us into the right direction (maybe a reference to a book or other document ?).
>
>Regards,
>
>Walter,