Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
One to many relationship but child in a different order
Message
De
18/02/2004 11:47:28
Cetin Basoz
Engineerica Inc.
Izmir, Turquie
 
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Divers
Thread ID:
00877599
Message ID:
00878363
Vues:
16
>Hi Cetin,
>
>The child grid I mentioned is an edit grid and as such needs to be ordered by two numeric columns on the grid. Do the edit grid allow this?
>
>Aso, I needed to add bmps to a grid as a sort of key for some mappoint automation I've been doing, and I found your excellent example of this in the FAQ.
>
>Is there any way of checking if a property already exists they you've added programmatically? I have to call the form init occasionally [dont ask :)] and obviously the propery is already created so I get an error. Can the property only be added to the container programmatically because I can't seem to do it manually in the form?
>
>TIA
>
>Best Regards
>Robin
>BSS

Oh editgrid. Then you need a workaround. You might use a combined key for ordering. ie: You want to order on dates entered but relation is through customerID which is numeric :

* Child table
index on padl(CustomerID,10,'0')+dtoc(myDate,1) tag myOrder

* Child Order : myOrder
* Relation (might do with RelationalExpr property)
set relation to padl(CustomerID,10,'0') into myChild

To check existence of a property you might use PemStatus() or type() function.
Cetin
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform