>I doubt, but as far as I know, MS does. But for example i don't want to include strict typing because VB, C, C++ has it.

I guess to we have to agree to disagree on this one, because strict typing is pretty high on my wishlist.

>If for example you want to write speach recognition into VFP, I'll say : let's do that with C, C++ or another language. If you want to store the spoken text you can write the DB part in VFP and let VFP communicate (DLL, COM, DCOM, ...) with this external program. Don't demand for native speach reqognition !

I won't. Each tool has it's speciality and this is not a speciality of VFP, I agree.

>I'm aware this remark rocks the boat, but I cannot see any case where I definitely want these methods. Sure, it can be easier than having propertie validation within ordinary methods, but I don't think the Assign and Access methods should be a part of the OO philosophy. And if it should, it should be implemented corectly. For example, I wrote a, assign method for the rowheight property of a grid. It DOESN'T fire when you interactively change the rowheigt.

You can write a perfectly good OOP application without using the Assign and Access methods. You can also mow the grass using a pair of scissors.

If there is a bug in a certain situation with the Assign method, don't use it in that situation and report the bug to MS. But don't boycot completly the Assign and Access methods because one has a bug in a certain situation.

>Could you tell me where it sucks. If they're valid, I'll pass them to Seagate.

I have to admit that I didn't use it in the past years. But the lack of an auto-align option in a visual reporting tool is a major flaw IMHO.