> I am accessing a *.cdb file on a flash card.
> Lets say, I
> -open a connection to this file
> -open a recordset with this connection
> - make changes to the records
> -close the recordset
> and then the power fails.
> Is the data cached or is it committed to the flash memory at this point.
> When is it actually "stored". Does it only happen when the connection is
> closed?
> I don't want to keep opening and closing the connection because I don't
want
> to worry about the CreateObject bug.
> Tony

> I am accessing a *.cdb file on a flash card.
> Lets say, I
> -open a connection to this file
> -open a recordset with this connection
> - make changes to the records
> -close the recordset
> and then the power fails.
> Is the data cached or is it committed to the flash memory at this point.
> When is it actually "stored". Does it only happen when the connection is
> closed?
> I don't want to keep opening and closing the connection because I don't
want
> to worry about the CreateObject bug.
> Tony

>I am accessing a *.cdb file on a flash card.
>Lets say, I
>-open a connection to this file
>-open a recordset with this connection
>- make changes to the records
>-close the recordset
>and then the power fails.
>Is the data cached or is it committed to the flash memory at this point.
>When is it actually "stored". Does it only happen when the connection is
>closed?
>I don't want to keep opening and closing the connection because I don't
want
>to worry about the CreateObject bug.
>Tony

> I am accessing a *.cdb file on a flash card.
> Lets say, I
> -open a connection to this file
> -open a recordset with this connection
> - make changes to the records
> -close the recordset
> and then the power fails.
> Is the data cached or is it committed to the flash memory at this point.
> When is it actually "stored". Does it only happen when the connection is
> closed?
> I don't want to keep opening and closing the connection because I don't
want
> to worry about the CreateObject bug.
> Tony

> I am accessing a *.cdb file on a flash card.
> Lets say, I
> -open a connection to this file
> -open a recordset with this connection
> - make changes to the records
> -close the recordset
> and then the power fails.
> Is the data cached or is it committed to the flash memory at this point.
> When is it actually "stored". Does it only happen when the connection is
> closed?
> I don't want to keep opening and closing the connection because I don't
want
> to worry about the CreateObject bug.
> Tony

> Hi Anthony,
> I think the problem is within the CEDB provider (CEDB database). I has an
> internal
> cache in memory which is only flushed when its full or the connection
object
> is released.
> Calling Update() in the recordset does not help. Also it seems to be a
> sequencial process,
> that means waiting some time after the update also does not help.
> Try switching to the SQL Server for WinCE. There data is updated direct
> (supposing
> you do not have a cache on the flash card) and you have much more great
> functions in
> the ADO interface and SQL statements.
> Someone told me that Microsoft was confronted with this problem by some
> system
> integrators at their last conference. Try looking up the quick fix list
for
> WinCE, maybe
> there is a fix for that now.

> Harald

schrieb

> > I am accessing a *.cdb file on a flash card.
> > Lets say, I
> > -open a connection to this file
> > -open a recordset with this connection
> > - make changes to the records
> > -close the recordset
> > and then the power fails.
> > Is the data cached or is it committed to the flash memory at this point.
> > When is it actually "stored". Does it only happen when the connection is
> > closed?
> > I don't want to keep opening and closing the connection because I don't
> want
> > to worry about the CreateObject bug.
> > Tony

> CEDB does cache the changes in memory, and it provides an API to flush the
> cache, but ADOCE does not make use of that API.  Believe me, Microsoft is
> aware of the problem. (If nothing else, this is a frequent question on
these
> newsgroups.)  I work on CEDB, not ADOCE, but I've passed the problem on to
> the right people and I'd be really surprised if the next version of ADOCE
> made the same mistake.  Not that I know when the next version of ADOCE
will
> be available.

> Sue

> _____________________________________________________________
> This posting is provided solely for informational use.  It is
> offered "AS IS" and with no warranties.   You assume all risk
> for your use. See full conditions for Terms of Use
> (http://www.microsoft.com/info/cpyright.htm)
> _____________________________________________________________

> > Hi Anthony,
> > I think the problem is within the CEDB provider (CEDB database). I has
an
> > internal
> > cache in memory which is only flushed when its full or the connection
> object
> > is released.
> > Calling Update() in the recordset does not help. Also it seems to be a
> > sequencial process,
> > that means waiting some time after the update also does not help.
> > Try switching to the SQL Server for WinCE. There data is updated direct
> > (supposing
> > you do not have a cache on the flash card) and you have much more great
> > functions in
> > the ADO interface and SQL statements.
> > Someone told me that Microsoft was confronted with this problem by some
> > system
> > integrators at their last conference. Try looking up the quick fix list
> for
> > WinCE, maybe
> > there is a fix for that now.

> > Harald

> schrieb

> > > I am accessing a *.cdb file on a flash card.
> > > Lets say, I
> > > -open a connection to this file
> > > -open a recordset with this connection
> > > - make changes to the records
> > > -close the recordset
> > > and then the power fails.
> > > Is the data cached or is it committed to the flash memory at this
point.
> > > When is it actually "stored". Does it only happen when the connection
is
> > > closed?
> > > I don't want to keep opening and closing the connection because I
don't
> > want
> > > to worry about the CreateObject bug.
> > > Tony