Graham,=20
First, for an "overview" of the capabilities of the cursor adapter
class, see my article in CoDe Focus:VFP 8, which is available online at
http://www.codefocus.com/.=20
Secondly, you won't have the same ability with the cursor adapter as you
have with ADO, unless you use ADO as your CursorAdapter data source. In
other words, you said you like being able to change the connection
string in order to connect to different data sources - with the
CursorAdapter, you can only do this with either the ADO or ODBC data
source types, as they're the only one's with connection strings to
change.=20
Using the CursorAdapter for XML support is a cool idea. If they're
implemented correctly, you can actually update an XML file or a stream
(such as from a web service or SQLXML) all through opening the
CursorAdapter and using TableUpdate. Pretty powerful, but really only
useful from the UI or middle tiers in a multi tier app - if you're not
multi tiered, then CursorAdapters are probably very useful to you.=20
So it sounds to me you might want to look into using the CursorAdapter
class with either ADO or ODBC as the data source, with an emphasis on
using the ADO data source (as you've used it before).=20
Hope this helps a bit.=20
-Chuck Urwiler, MCSD, MCDBA
http://www.eps-software.com
-----Original Message-----
From: Graham [mailto:gbrown AT compsys .D.OT co.uk]=20
Sent: Wednesday, April 30, 2003 4:22 PM
To: profox@leafe.com
Subject: re: Codemine 7 and VFP8
Hi Jim
Thanks for that.
According to Codemine support Cursor Adaptors are only used for XML
support. I cannot vouch for this until I have had chance to read
Tamar's book (on order from Amazon) to see if that sheds any light.
My limited knowledge of this is that the idea behind C/A's is to
encapsulate the behaviour that reads from and writes to the backend
without having to use "USE TABLENAME" or SQLExec type commands. This
populates what are extensibly views and by setting the necessary
properties controls how the data is written back to the database.
What I am trying to do is have one front end (vfp) that can talk to any
number of backend databases *without* having to have convoluted case
statements. This would be similar to the RDD technology that existed in
Clipper back in the mid 90's!!
My daytime job as opposed to the consulting company I run writes in
Active Server pages and ADO, this means that by changing the connection
string I can effectively talk to any backend database. I've written a
couple of functions that deal with the idiosyncrasies of each ie dates
are delimited with a ## in Access {} in fox and '' in SQL. As new
databases are required I normally only need to get the new connection
string and change the two interface functions if necessary.=20
This works! and it is incredibly simple to bring solutions to market.
This is the utopia I am trying to find with Fox and everything seems to
be that you have to maintain different code for each backend.
Inviting comments/flames/bricks through the window etc etc!!
Regards
Graham
>>It is not that it isn't compatible, it was due to code specifically in
>>CodeMine that checked for the version of VFP and would only let you
run with
>>VFP version 6 or 7 (to prevent people from trying to run in under VFP
3 & 5,
>>which would not work because CM used VFP 6 specific syntax). All
version
>>7.1 does is include VFP version 8 as an allowable version.
Jim Kearns
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
[excessive quoting removed by server]
©2003 Chuck Urwiler |
