Xref: utzoo comp.databases:2840 comp.sys.ibm.pc:30716 comp.dcom.lans:3068
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!columbia!cs!benderly
From: benderly@cs.columbia.edu (Dan Benderly)
Newsgroups: comp.databases,comp.sys.ibm.pc,comp.dcom.lans
Subject: Re: Concurrency Control in DbaseIII+ or Paradox...
Message-ID: <261@cs.columbia.edu>
Date: 28 Jun 89 04:21:58 GMT
References: <25232@shemp.CS.UCLA.EDU>
Reply-To: benderly@cs.columbia.edu (Dan Benderly)
Followup-To: comp.databases
Organization: Columbia University Department of Computer Science
Lines: 19

In article <25232@shemp.CS.UCLA.EDU> gblee@CS.UCLA.EDU (Geunbae Lee) writes:
>Please consider the following problems:
>We have one file server(ibm ps/2) and two workstations (ibm at and xt) 
>connected using Novel Advanced Netware. The server machine
>is running dbaseIII+ or Paradox. Now, we want our 3 personell 
>simultanously acess the database file on the server and modify it and
>do whatever he/she wants. I know this is the basic concurrency
Description Omitted .....


Paradox has a network version (at least in 2 it did -- I think in 3 it comes
with the single-user package, but you have to buy more lic\scences for multi
-user operations).  Anyway, Paradox has a co-edit mode, which allows multiple
people to access the same data file, and locks users out only when necessary.
The screen is updated with thenew data periodically.

Dan

benderly@cs.columbia.edu