You are right, but what I want isn't append, I want to insert after
the current record, not in the end of the dataset. It seams that what
I need is a new button option to TDBNavigator, maybe nbInsertAfter.
--
Felipe Monteiro de Carvalho
___
fpc-pascal m
On Mon, 5 Oct 2009, Felipe Monteiro de Carvalho wrote:
On Mon, Oct 5, 2009 at 3:24 PM, David Emerson wrote:
Maybe you could do a sync operation or some such, to force changes to be
written to disk. It would probably slow the system down, but you might
be able to get it to work.
Yes, but th
On Monday 05 October 2009 15:44:55 Felipe Monteiro de Carvalho wrote:
>
> Is it possible to have 2 dataset objects sharing the same memory
> database? Or else any ideas of how to solve this problem other then
> constantly writing changes to the disk and reloading the read dataset?
>
tmsebufdataset
On Mon, Oct 5, 2009 at 3:24 PM, David Emerson wrote:
> Maybe you could do a sync operation or some such, to force changes to be
> written to disk. It would probably slow the system down, but you might
> be able to get it to work.
Yes, but that's quite ineficient. I already have the data in memory
En/na Felipe Monteiro de Carvalho ha escrit:
The problem now is that the write doesn't go immediately to disk, so
How so? If you're using a database server (or sqlite), any connection
should see the modifications as soon as the transaction is committed (in
fact the data or the journal shoul
On Mon 5 Oct 2009, Felipe Monteiro de Carvalho wrote:
> The problem now is that the write doesn't go immediately to disk, so
> when modifications are done this doesn't modify the displaying of data
> which is based on the read dataset.
Maybe you could do a sync operation or some such, to force cha
On Mon, 5 Oct 2009, Felipe Monteiro de Carvalho wrote:
Hello,
I am having a dilema with a dataset based app. I have 2 dataset
objects pointing to the same database file, one connected with
data-aware controls to allow the user to change the data and the other
one only for reading. I need 2 be
Hello,
I am having a dilema with a dataset based app. I have 2 dataset
objects pointing to the same database file, one connected with
data-aware controls to allow the user to change the data and the other
one only for reading. I need 2 because I need to show data based on
the database while modify