>FYI, I'm planning on writing a review of Oakleaf's ON-LINE .NET for Visual FoxPro Developers training that I'm taking next week. I hope I'm not expecting too much out of it, but I'm looking for it to really jump start my immersion into .NET. I'll be as comprehensive as I can and try to give enough information for someone else to make a decision on taking the training themselves. I'll probably wait until next week to do the review. Kind of like getting a haircut; it almost always looks good right when they cut it, but what about a few days later when all the glitz and mousse is gone?
>
>If you want some advice - in this general situation, if you write your review weeks or even months later, you're more likely to write one with value.


Why is that?