Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
CursorAdapter vs Data objects.
Message
From
21/10/2009 07:22:23
Walter Meester
HoogkarspelNetherlands
 
 
To
21/10/2009 02:21:12
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Germany
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9 SP1
Miscellaneous
Thread ID:
01430032
Message ID:
01430329
Views:
80
Hi Agness,

>some minor stuff like SendUpDates and AllowUpdate, -Insert, -Delete. (If you miss)

??? What is up with these properties ???

>What I found tricky to is that a DE will open the adapters in the order of there ZORDER. This is very intuitive and easy to change. (I've skiped it and use a classfactory to add the CA's on runtime. I don't use SCX, so I can not drag - drop anyway)
>The common problems of views on creating new records on the view like receiving the PK, problems with AutoInc remain.
>It is tricky to write multiple tables. (Ok write is no problem but the errorhandling)

We are not using the DE, so that should not be a problem for us. We are using a function to get a newkey for the keys in the cursorschema (just like we did with SQL views). BTW, I think there is an article from Calvin Hsia somewhere that describes how to get the key from the backend when its generated by the database itself.

>I do not use triggers, so I have no idea how this will work.

>I found it uneasy to fill the properties directly, its very hard to follow. I have a method where I fill all the props via string operation. The logic is inherited from Mark McCaslands CursorAdapter VCX Builder Download#17264. I found this tool very usefull and have altered it so that it creates the DE, CA's and my factory entries from the cursors of an open datasession. This was very helpfull converting my view based apps to CA based.

I See.

>Update
>
>the tableupdate problem
>tableupdate() returns .T. if the cursor itself is updated. This does not mean it is written to the source. You would need something like
>
>llx1 = TABLEUPDATE()
>llx2 = _TALLY#0
>
I thought this only was a problem in VFP8 and resolved in VFP8SP1. No?

In VFP9SP1 Tableupdate returns .F. when I try to tableupdate a change while the change was rejected by the backend.

>As far as I see my code INSERT via TABLEUPDATE will made it even more tricky.

???

All in all... Are you satisfied with CA's? Are you using it in a mission critial application. Any other real life issues with it?


Walter,
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform