On 11/19/2014 03:18 PM, Mike Morris wrote:
> I've written a small tool to allow editing some Foxpro DOS 2.6 tables.
> Some columns have been added to the tables since the app was written,
> and the original FoxPro app does not support editing them. The pydbf
> tools provides write access to those fields, and works perfectly when it
> is the only app accessing the tables.
>
> However, when using the pydbf tool while there are instances of the
> original application open, results are very inconsistent.
>
> Various results in multi-user situations include:
>
> * the record is updated immediately (actually, within the SET
> REFRESH() time of the original app)
> * it updates when the original app *on the same workstation as the
> pydbf tool is running* is closed
> * it updates only when all instances of the original app are closed
> * it never updates at all
>
> I have not conducted rigorous testing, so I can't really *swear* by all
> those results, but it's definitely inconsistent, and presumably
> dependent upon the lock state of the table/record in running instances
> of the old app... but I'm hoping I can figure it out by just
> understanding any multi-user related pydbf behavior :-)
My experience is that dbf only really works for multi-users when they
are logged into and accessing through a single application. My worse
case experience is corrupted dbf files.
>
> Thanks in advance - and thanks for the pydbf tool, it's great!
>
> --
>
> ---
> You received this message because you are subscribed to the Google
> Groups "Python dBase" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
python-dbase...@googlegroups.com
> <mailto:
python-dbase...@googlegroups.com>.
> For more options, visit
https://groups.google.com/d/optout.
--
Adrian Klaver
adrian...@aklaver.com