Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Difference between Single user Grid and Multiuser grid
Message
 
To
03/02/2007 10:16:02
Mike Yearwood
Toronto, Ontario, Canada
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Network:
Windows 2000 Server
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01190788
Message ID:
01192107
Views:
22
Well, we'll have to agree to disagree. I think your admonition against PVs is unfounded. You just have developed a technique that you like and now you think everyone should use it - that does sound biased. Developing always in multiuser mode is a great thing. But having to do all querying in a certain way is just your personal preference. And to say that having different ways to query data within the same app is asking for trouble is also unfounded. As long as the techniques are used soundly, there is no reason that it is "asking for trouble." I actually edited my original comments to take out the statement that you were dissing PVs, thinking that may not have been accurate, but your reply seems to support that original comment.

>Ah. I understand. IMO PVs are so common they're a defacto standard. I'm not dissing them. It's not possible to diss something abstract like a technique.
>
>BIAS: a particular tendency or inclination, esp. one that prevents unprejudiced consideration of a question; prejudice.
>
>I don't have a bias against PVs. I've got considered reasons to avoid them.
>
>I look for techniques which can be applied to all situations. Multi-user is a technique that can be used in all situations. Single user cannot.
>
>Seems to me having a system with PVs, CAs, SPT, SEEK etc. is just asking for trouble. User requirements have little to do with implementation.
>
>I used PVs before and even advocated them. I grew out of them in favor of SPT or CAs. The dynamic macrosubbed where clause of the view was awkward at that start, then VFP changed how it had to be done. Yuck. The whole view designer was broken for a long time. Views have limitions like the one I pointed out. They're easy, sure, but easy seldom equates to optimal.
>
>Lots of programmers build systems where the user cannot do their own searches (excepting reports). PVs work fine like that. I think it's wrong to limit the user like that. PVs aren't flexible enough.
>
>I won't go out on a limb and say they're obsolete, like Naomi did with SET FILTER :), but for new development, I'd recommend against PVs.
eCost.com continues to rip people off
Check their rating at ResellerRatings.com
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform