I keep finding that using the VFP 9 report behavior I end up with more problems that it's worth. I could be doing something wrong, but settings that worked fine in the past now don't work. And this is not using any Report Listener functions. If I needed to do something advanced enough to require that, then I'm sure the tradeoffs would be worth it, but at the moment, with fairly standard reports, the new behavior is misbehavior, IMHO.

For example, I have a straightforward inventory report I'm creating. There's a quantity column. This company carries a lot of unique items, so most of the time the qty. will be 0 or 1, sometimes 2. However, they do carry some things that are manufactued goods, so in some categories they might have qty. in the hundreds. The field for qty. on the report is about 4 characters in width. With "stretch with overflow" turned on, the qty. prints fine, but the number doesn't align properly with the column heading (I'm right aligning and testing with an inventory category where the qty. values are 0, 1, or 2). With "stretch with overflow" turned off (in an attempt to get the alignment correct), all I get is asterisks! It's irritating when a single digit number can't be made to fit into a field that is 4 characters wide. It seems that the default trimming has to be changed to something like "trim to nearest character, append ellipses" in order to get it to work, but then I'm back to the bad alignment. I'm not sure why default trimming causes this issue. It seems to use VFP 9 report behavior you have to do a lot more tweaking and testing for not much benefit.

Russell Campbell