Michael, > I agree that it shouldn't be a requirement. All I was saying > is that if you start out with the N-Tier approach, it makes it easier to > prototype in VFP and then upscale to C/S if you need to do so for whatever > reason. That's all. I wasn't saying one way was better than > another.
> I was merely commenting on the design approach. > > I agree that the SMBs are my preferred customer, too. Then we're in basic agreement. Bear in mind that this thread was started by Jeff asking how to deal with large databases and I suggested that he's better off breaking the tables up then moving the database to a backend DBMS. I said this from the position of a VFP shrink-wrapped product vendor, which I'm not sure is Jeff's orientation. But it is yours, so we went on a bit of a tangent from the original question. What else is new? :) On C/S and VFP product positioning, Jeff's case does serve to illustrate my point that our VFP product customers aren't going to run into much trouble getting our stand-alone products installed, but can have great obstacles if doing so entails a backend DBMS. This argument notwithstanding, I am using MySQL, but only for add-on features where I manage the inet installed database. Bill _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
