Or change to Interbase and open up a whole new world for yourself. No more
BDE. No more concurrency issues. No more lost or corrupted data.
T
----- Original Message -----
From: "Stephen Barker" <[EMAIL PROTECTED]>
To: "Multiple recipients of list database" <[EMAIL PROTECTED]>
Sent: Friday, July 06, 2001 10:27 AM
Subject: RE: [DUG-DB]: Updating physical tables
> Make sure you have BDE config setting LOCAL SHARE = TRUE on all pc's
sharing
> this data.
>
> After posting, try dbisavechanges(...). Although closing the table should
be
> enuf.
>
> regards,
> Steve
>
> > -----Original Message-----
> > From: John Christenhusz [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, 6 July 2001 08:13
> > To: Multiple recipients of list database
> > Subject: [DUG-DB]: Updating physical tables
> >
> > G'day folks,
> >
> > This is paradox question. When I modify a record from a table and post
it,
> > the physical table has not been updated yet. I assume the DBE keeps it
in
> > memory till the application is shut down or that there is enough changed
> > data worth starting the actual save procedure.
> >
> > 1. Is this assumption correct ?
> >
> > 2. How can this be solved so that the physical table is updated when I
> > want it to be available for other external purposes? (note that an close
> > table - open table doesn't seem to work).
> >
> > 3. Is there any way to detect if the physical table is not updated yet?
> >
> > TIA
> >
> > John.
> --------------------------------------------------------------------------
-
> New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
