Microsoft Knowledge Base Email Alertz

KBAlertz.com: If you use the One-to-Many Report Wizard to create a report and specify a view for both the parent and the child table, you will be unable to modify or print the report after creation. The following error occurs when the report is modified through the...

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 135563 - Last Review: February 11, 2005 - Revision: 4.1

FIX: One-to-many report that is based on two views causes errors

This article was previously published under Q135563

On This Page

SYMPTOMS

If you use the One-to-Many Report Wizard to create a report and specify a view for both the parent and the child table, you will be unable to modify or print the report after creation.

The following error occurs when the report is modified through the menu, or through a MODIFY REPORT command:
The Child Order property of a relation object in the data
environment is no longer valid. The relation is being removed.
The following error occurs when the report is printed through a REPORT FORM command:
Index tag is not found.

CAUSE

A one-to-many report relies on a relation between the parent and child table. It is impossible to create a persistent relationship based on two views in the data environment because views are not indexed. This is by design. However, the wizard fails to check whether the tables specified in the report are actually views. When the report is modified or printed at a later date, the errors occur.

WORKAROUND

Specify a .DBF table for both the parent and the child table in the wizard. If you're using a view to limit the scope of the records included in the report, consider using a SET FILTER condition or the FOR clause of the REPORT FORM command to limit the records included in the printed report.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem has been fixed in Visual FoxPro 5.0 for Windows.

MORE INFORMATION

Steps to Reproduce Problem

  1. Open the vfp\Samples\Mainsamp\Data\Tastrade database.
  2. On the File menu, click New Report and then click the Wizard button.
  3. Select "product listing" from the list of available tables as the parent table. Add all fields to the list, and click Next.
  4. Select "order history line items" as the child table. Add all fields to the list, and click Finish.
  5. Select the Save Report option, and exit the Report Wizard.
  6. Attempt to modify or print the report. An error will occur.

APPLIES TO
  • Microsoft Visual FoxPro 3.0 Standard Edition
  • Microsoft Visual FoxPro 3.0b Standard Edition
Keywords: 
kbbug kbfix kbvfp500fix KB135563
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please