network paradox table

Hi there



I am trying to get my program to work over a network. I use paradox tables,
I have 2

systems, one has the program and data installed on it and the other has just
the program

and the tablename is pointed to the data on the first system



Both systems will read the data correctly, but if a make a change to the
data on either

system the other one will not pick up the changes unless I close the program
and reopen it

I have FlushBuffers in to force it to update the table but this has not
worked, it seems to me

that the program is holds the data in memory, is this a setting I have
missed somewhere to stop this?



Also I have been looking round the net and can't find an answer, but is
there a way

I locking a record so that if one system is editing it the other system can
only read it?



Many thanks



Brian






.

Relevant Pages

  • [RFC][PATCH 0/9] Network receive deadlock prevention for NBD
    ... Convergence of network and storage paths" ... "Net vm deadlock fix " ... Maybe it is another memory deadlock, ... dipping into the memalloc reserve if it must. ...
    (Linux-Kernel)
  • Re: [PATCH] [Request for inclusion] Filesystem in Userspace
    ... > to allocate network buffers down to the PF_MEMALLOC boundary. ... > the network stack is only allowed to allocate memory down to the ... A lot of people think that mempool solves this problem, ... normal allocation, but that fails, so they start eating into the mempool ...
    (Linux-Kernel)
  • Re: [RFC 0/3] Recursive reclaim (on __PF_MEMALLOC)
    ... then you should not kill the other things that want memory. ... The users of memory are various subsystems. ... the network subsystem because its build on kmalloc! ... The reserves are spread over all kernel mapped zones, ...
    (Linux-Kernel)
  • Re: Odd performance problems after upgrade from 4.11 to 6.0-Stable
    ... After the upgrade, the system performs poorly. ... job produced minimal CPU utilization and little progress. ... My network link only ran at 3.4 Mbps (yes, that's bits, not ... runs out of memory and starts to use the swap file. ...
    (freebsd-stable)
  • [PATCH 02/20] net: vm deadlock avoidance core
    ... the block device must never stall because of ... that it must always find enough memory to build/send packets over the network ... Memory pressure will add to that; what if there is simply no memory left to ... goto nodata; ...
    (Linux-Kernel)