Silvain,

>>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.

I'm surprised that you want strict typing. I've programmed in C, C++ and I really felt that it was just a pain in the butt. VFP becoming strict type, it loses the charm of the xBase languages. But O.k. I agree to disagree.

>>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.

I learned the OOP pricipals at universaty, But the assign and access was new to mee when I looked at Visual Objects For Clipper. Seeing how my colleage abused this feature to write programs, I began to dislike this feature, overall it can be simulated real easy, (as for the static memvar variable).

>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.

It's not a bug. It's a design error. The access and asign methods (I admit I haven't checked this througely) only fires on xbase code, not on internal C++ code. Can you describe a situation where you definitely want to use the assign and access methods ??

>>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.

Version 7.0 is pretty good. Though you can align controls with tabs on the rulerbar and have a align to grid feature, it misses features found on the aligning toolbar of VFP. Though this is irritating at first, there are lots of features that are far more user-friendly than the VFP report writer (changing lay-out in the preview mode).

to name a few others:
- changing the zoom mode from 25 - 400% (programmable)
- Programmaticly assign a printerdestination to the report to print.
- Easy programmable way to change paperformat and destination.
- Use of subreports into one report (Multi detail band feature).
- You can place the preview in any window you like.
- Export to numerous formats, including Word, Excel, HTML and RTF.
- Find text in the preview.

Isn't this what we wanted in VFP for years ?

Of course there is alway's something to complain about, but overall CR 7.0 is a far better report writer than the native VFP one.

Once you've written your classes to intergrate CR into VFP it's almost as easy as calling a VFP report.


Walter,