In one of those typical "my language is better then yours to do X" discussions with a friend, I opened up the Report Wizard to show how fast someone new to the language could put together a report with it. Admittedly, I don't use the report wizard when I write my reports, but I was heading for a certain "wow" factor. Unfortunately, the wizard blew up. Using sample database and sample data supplied with VFP 9! I've ferreted out why, but thought I would put it on here in case anyone else decides to use the wizard tool can navigate around the error.

Steps to replicate:
1) test database with a integer pk's and fk's (I used the campagn database created using the project wizard and selected it to autofill some data for me)

2) Select the report wizard and choose the one-to-many report wizard

3) Select fields from parent and child tables as indicated in the wizard

4)Relate tables (I used donorid to relate the Donor and Pledge tables)

5) sort records (I used donorid, the integer pk of the donor table)

6) on the report style tab, select the button "Summary Options" I chose to SUM the amountPled field with the detail and summary option group selected.

If you preview the report here and scroll to the last page, it will blow up with "Error #107 in process (0):Operator/operand type mismatch.

If you save and modify in the report designer first, you will notice in the group footer 1 which is reset on my integer donorid has a field in it with the following expression:

[Subtotal for ]+donorid+[:]

This is what is causing the operator/operand mismatch.

Opening it up and adding a transform() to the donorid fixes it. Whereas I understand having the report show "Subtotal for 5:" would make no sense to an ultimate user, it would have been less embarassing my show and tell if the wizard took into consideration someone may have an integer value used there.

Forgive me if all of you already are aware of this issue, I just wanted to tell someone. .