Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Interface ideas needed
Message
 
 
À
19/02/2001 11:19:25
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Divers
Thread ID:
00476845
Message ID:
00477513
Vues:
27
Hi Dragan,

>>>One thing to keep in mind - what's "user" in your case? The whole of all users within one customer entity, or any individual? The difference is in the way you should store these - if there are many users with their own regionalizations, you'd have to have a regions-per-user table as a parent to keep the region names, and city-per-region-per-user as a child table; if there's only one regionalization per customer, you need only the first one, and only add the region code into cities table.
>>>
>>In my first message I didn't say the whole truth :) There are four applications actually involved.
>
>Still, this doesn't answer the question on top of the quote above, which will only influence your solution in the end. If your four apps impersonate different users in this case, i.e. they have regionalizations of their own, or if they all use the same regionalization - that's something which will influence the way you'll store the city-belongs-to-region data.
>

As far as I understood, user = customer in my case. We have separate customer table already. Customers for this particular report would be in this table too (of course, other customers are interested in other products). Hopefully, each individual customer would have only one Regions definion (IOW, no multiple region definitions per one customer). Therefore, the idea of storing:
Parent Table: RegionID CustomerID Region Details
Child Table: RegionID Town (code) City County etc.
should work.

>It's really tough to be talking about things like this at an abstract level, because we tend to use some real-life situations and/or entities just to symbolize certain types of use or relations between entities etc, which is helping in a way, but also distracting. I can't seem to find a common denominator for all of cases like that - sometimes we do get the message through really easy, sometimes we have to pull up the details like you just did, and still aren't sure the message got through :).
>
>Well, I hope all of this talk gives you a good headstart. Good luck.

Thanks a lot for the help. BTW, I was at work today (but just briefly, since our Care Provider left for a weekend and we were not aware about it) and I saw 2 messages in my e-mail related to this topic. I will study them, but just would like to thank Jeff and Sergey for sending me them.

Thanks.
If it's not broken, fix it until it is.


My Blog
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform