Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
N-Tier Design
Message
De
18/09/2003 11:17:45
 
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
Divers
Thread ID:
00830147
Message ID:
00830328
Vues:
15
Your users will need to change the way they work to use sets of data. In my experience, users have found using sets much easier. For example, you can have a query where all customers in a particular city are returned. In this case, record navigation works on the set of data, not the entire table.

>I agree that I will need to move my app to VFP8. And I agree that is seems that XML is a good way to move data between UI and BIZ tiers. But ..<g>
>
>My problem is that I am concerned how this change will effect the UI tier (which what customers see). You see, my UI forms allow customer to view the entire table (even if it has 200,000 records). That is the form has navigational buttons <1st,Prev,Next,Last> and a grid where it is easy to move to any record with just a click. If I separate the UI from the tables, the UI will have to make a lot of trips to data/biz tier to get data as the customer wants to see different records. Performance will probably suffer. And I don't even know what to do with the grid. So a lot to think about.
>
>
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform