<i><font color="#663300"><i><font color="#663300">
If this is true, then we can't really making an efficient app using ODBC. The only way to avoid this, is to have a backend database that is not based on flat files, e.g. SQL Server, Oracle
Gracie</font></i>
Yes and No... it is not so much an issue of using flat files, as the fact that you are using VFP. Whether you use VFP nativly or it's ODBC driver, the database engine runs on the client.
Some where this concept of using VFP ODBC somehow makes things client server has confused alot of people. There is also talk that it is faster over a slow connection to use the ODBC driver than native access. Which may be true, but the difference is going to be minimal.
Now, that being said, you don't have to go to SQL or Oracle to have a true client server architecture. There are several ways to do this with VFP.
I think the simplest approach is one that Les Pinter did an article and wednesday night lecture on a few months ago. You can find out about it at http://fox.wikis.com/wc.dll?Wiki~UsingWebConnect . Also, Rick Strahl wrote a similar white paper you can find at http://www.west-wind.com/presentations/wchttp.htm .
Both of these article discuss the concept of building a client/server ap where both the client and server (with the help of a web server) are implemented with VFP. Les Pinter has a very simple set of classes and he says he can retrofit a VFP in about 20 minutes.
IF you want to use Codebook with these methods you could. You may even find that you could create a data behavior class that uses this technique.
Hope this helps,
BOb
</font></i>
OK, let's just say that we are using Oracle or SQL Server for this client server arrangement, because we do not have a choice. =)
What advice is there for these almost intolerably slow ODBC connections?
What other datasource sources can be used?
Is there a way to limit the number of records retrieved, especially in a situation where I only initially need the one parent record, but all the resulting child records?
It just so happens I just ran into this wall in my application (now that I figured out how to use the upsizing wizard in VFP, which also runs so slow I have to leave it to run over the weekends for some of the larger tables). The response time from my remote views is presently unacceptable and I have to believe that there is a better, or at least a more acceptable way to do this. I would love to hear about any other alternatives.
Devman
mdevlin (AT) ajdebruin DO.T com
©2002 Mike Devlin |
