Jeff Johnson wrote: > Steve: I just picked up a job re-writing a web application using VFP. It > was written in .NET for the desktop. Compare navigating web pages vs. VFP > with multiple windows open. It was an easy sell for me. Also, reports > never worked right. > > We have one application on terminal services and it has a whole new set of > problems besides having to deal with passwords expiring, Networking taking > the system down, system backups and maintenance interfering with the 24/7 > operation just to name a few. > > If the application will be used on desktops and intranets, I prefer a > desktop application. If it is a web application, then I would prefer the > web. > >
Jeff -- this is why I like the idea of using VFP app on the client side with a MySQL (or PostgreSQL, etc.) database hosted on the web. The client gets basically a networked application that works across locations, and the rich/smart client UI instead of a clunky browser interface, and snappy performance yet at that (of course assuming you've designed it properly and aren't wasting bandwidth). Mind you my clients are SMBs (mostly small), so it's not like there's gazillion records to deal with anyway. -- Michael J. Babcock, MCP MB Software Solutions, LLC http://mbsoftwaresolutions.com http://fabmate.com "Work smarter, not harder, with MBSS custom software solutions!" _______________________________________________ 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.
