Nope. Is that required?
Yes is. TSQLQuery is descendant of "buffered dataset" so all changes
what you do are cached localy until they are applied to remote database.
ApplyUpdates does it ...
How does that factor in to accessing the data through bound controls?
Bound controls have nothing with it ;-)
L.
Thanks.
Nathan T. Wild
On Mar 13, 2014 9:57 AM, "LacaK" <la...@zoznam.sk
<mailto:la...@zoznam.sk>> wrote:
Nathan Wild wrote / napísal(a):
I have been transitioning my work over from Delphi to Lazarus.
For the most part it has been smooth and satisfying
experience. I'm loving Lazarus and FPC and being unburdened
by closed source proprietary stuff in general.
The majority of the work I do requires connections to a
Pervasive database (from Btrieve v6 all the way up to the most
current). I should be able to do this via ODBC. I have no
problem reading data, executing queries, etc. but as soon I
try and act on a TSQLQuery using methods like .Delete(),
.Append(), etc. everything appears to work fine, but as soon
as the dataset refreshes my changes disappear. I can write to
the same tables using INSERT, DELETE and UPDATE queries
without issue.
Do you use TSQLQuery.ApplyUpdates followed by
TSQLTransaction.Commit or CommitRetaining ?
-lacak.
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
<mailto:fpc-devel@lists.freepascal.org>
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
------------------------------------------------------------------------
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
