Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Design of table relationship
Message
 
À
27/05/2002 09:54:38
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivie
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
00661654
Message ID:
00661817
Vues:
20
Hillmar said:
>I don't quite understand what is the basic difference between the two approaches, or what is the underlying philosophy of each approach.

Well, I realize now that I did not explain that very well.

The first version has one record per service location with three fields for address codes (only the first of the three is required). The code is the link to a record in the address table.

The second version also has one record per service location, but the existence of more than the required one address is evident only in the address table. The type of address a that a record represents is denoted by a .T. in one of the logical fields.

Does that make more sense?

>For now, let me remind you that you can put the address in a single memo field. Two or more "adress lines" in separate fields seem, to me, more difficult to manage.

Agreed. I will consider doing that for this database.

Thanks,
Randy Bosma
VFP - Because life is too short to code in something else...
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform