Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Multiple detail bands
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire de rapports & Rapports
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP
Network:
Windows 2003 Server
Database:
Visual FoxPro
Divers
Thread ID:
01246721
Message ID:
01246877
Vues:
26
This message has been marked as the solution to the initial question of the thread.
>I populate a cursor for each detail band. The parent cursor is "aporg" and to create the deduction cursor "adeduc" I use the following query:
>
>INSERT INTO adeduc (pd_phaccno, pd_name, pd_value, pd_ivat, pd_glkey, pd_drcr) ;
> SELECT pd_phaccno, pd_name, pd_value, pd_ivat, pd_glkey, pd_drcr ;
> FROM bkplpayd, aporg ;
> WHERE bkplpayd.pd_phaccno = aporg.ph_accno and pd_delflag != .T. ;
> ORDER BY pd_phaccno
>
>The records in adeduc is correct (4 records), but for some reason additional records were inserted into aporg, but containing only '**********'. The report prints correct (excluding the '****' records), I'm just worried that the cursor can become were large.
>
>What can I do to prevent this?


Are you sure the record are really inserted in aporg .. or are you browsing the table which has some relations and skip to settings that are just letting you see the records and their relations. IOW .. the **** records aren't really in the table, it's just that the browse is showing you a repeat of the parent table in the relation.
Cathy Pountney, Microsoft Visual FoxPro MVP
Memorial Business Systems, Inc. (www.mbs-intl.com)

My Website: (www.frontier2000.com)
My Blog: (www.cathypountney.blogspot.com)
My Book: The Visual FoxPro Report Writer - Pushing it to the Limit and Beyond
Free MSDN Article: What's New in the VFP 9.0 Report Writer
Free MSDN Article: The VFP 9.0 Report Writer In Action
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform