Francisco Tapia
fhtapia at gmail.com
Thu May 18 17:33:40 CDT 2006
Thanks Jim, I know that I'm going to be working with the vendor, on the basic optimization points that they need to work on. One step that should be automated is the re-indexing that they perform every tuesday. :| On 5/18/06, Jim Dettman <jimdettman at earthlink.net> wrote: > Francisco, > > VFP is pretty much like Access; a "default" database engine that is > integrated with VFP. It is considerably faster then JET. Processing is > client based. > > VFP can also use BE database engines such as mySQL, SQL Server, etc. using > remote views or the cursor adapter. This is where the VFP community is now. > Most, except for small apps, don't use the default engine any more as this > moves them to client/server computing. > > Overall, VFP and Access share similar overall concepts, but with VFP, > there is just about nothing you can't fiddle with. It has a richer event > model and the programming language has more features and commands, and of > course VFP is totally OOP based. > > The data environment for forms is something I'd kill for in Access. On > the down side; the query designer does not work as well as Access's and the > report engine I feel is weaker (although you can do a drill down report if > you want to). Then there are some just plain weird ways to do things, like > adding a column to a grid control, or changing the text of a label on a > report. > > VFP started as a DOS based tool and it shows. Most developers skip the > visual aspect and make heavy use of the command window. As a result, the > visual design tools are not up to what they should be. > > Overall much more of a developers tool then Access. STEEP learning curve; > figure on using it for a year at least before you'll be somewhat proficient. > Also, use of a framework of some type is almost a given. > > Jim. > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia > Sent: Wednesday, May 17, 2006 1:37 PM > To: Access Developers discussion and problem solving; > access-l at peach.ease.lsoft.com > Subject: [AccessD] Foxpro > > I'm getting ready to begin working on a "foxpro" db. It's been a > really long time since I've used a foxpro db, last time was somewhere > in 1992. One question that arose, is in a client/server app is the > processing done on the server or the client like access? > > Thanks, > > -- > -Francisco > http://pcthis.blogspot.com |PC news with out the jargon! > http://sqlthis.blogspot.com | Tsql and More... > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More...