Microsoft Knowledge Base Email Alertz

KBAlertz.com: If you specify a view as the child table in the One-to-Many Report Wizard, and then click the Preview button on the final step of the wizard, this error occurs: Error 1683 in process (0); Index tag is not found

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: 134437 - Last Review: September 30, 2003 - Revision: 3.1

FIX: Report Wizard Preview Error If View Given as Child Table

This article was previously published under Q134437

On This Page

SYMPTOMS

If you specify a view as the child table in the One-to-Many Report Wizard, and then click the Preview button on the final step of the wizard, this error occurs:
Error 1683 in process (0); Index tag is not found

CAUSE

By design, a view cannot be used as the child table in a one-to-many relationship. This is because the child table must have an index tag on the parent table key field in order to create the relationship. Because a view cannot be indexed, the relationship cannot be created.

The One-to-Many Report Wizard does not check to see if the child table is a view or an actual table. When the preview button is clicked, the error occurs.

WORKAROUND

Be sure to specify an actual table for the child table prior to invoking the wizard.

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 Behavior

  1. Open the Tastrade.dbc database in the VFP\Samples\Mainsamp\Data directory.
  2. On the File menu, click New Report, and then click the Wizard button.
  3. Choose the One-to-Many Report Wizard.
  4. Specify Products as the parent table, and include all fields.
  5. Specify Order History Line Items as the child table, and include all fields.
  6. Click Finish.
  7. Click the Preview button. The error should occur.

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

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