From: "Michel Walsh" References: Subject: Re: What is the best way to handle client/server envirnment for ten or more computers in a network using it constantly.. Like Supermarket.. Date: Mon, 24 Nov 2003 07:30:13 -0500 Lines: 34 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: <#fZiZZosDHA.2440@TK2MSFTNGP12.phx.gbl> Newsgroups: fj.comp.lang.visualbasic,microsoft.public.access.modulesdaovba,microsoft.public.access.modulesdaovba.ado,microsoft.public.activex.programming.scripting.vbscript,microsoft.public.vb,microsoft.public.vb.3rdparty,microsoft.public.vb.addins,microsoft.p NNTP-Posting-Host: 199.243.131.42 Path: ccsf.homeunix.org!ccsf.homeunix.org!news1.wakwak.com!nf1.xephion.ne.jp!onion.ish.org!onodera-news!Q.T.Honey!komachi.sp.cs.cmu.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeeds.sol.net!news-out.cwix.com!newsfeed.cwix.com!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl Xref: ccsf.homeunix.org fj.comp.lang.visualbasic:33 Hi, XP is 2000 with some minor improvements. If you write to the database (JET or MS SQL Server) in a multiple users environment, you may specify which type of record locking (optimistic or pessimistic) you want in order to avoid incoherence when the two users write more or less at the same time on the same record of the same table. You get run-time trappable error (through an Access Form OnError event, or through the standard on error handling if you are outside an Access Form) and there, you can resubmit the "operation", as it fit your need, or cancel it (if that is how it should be done). Hoping it may help, Vanderghast, Access MVP "Victor Cheung" wrote in message news:hS%vb.2256$Fv8.150@twister01.bloor.is.net.cable.rogers.com... > I developed the software with microsoft access.. and windows XP.. but.. > Windows XP give me hell... so.. probably use Windows 2000 Professional.. > which I think is a better OS.. i guess.. my question is how can i avoid.. > the problem when two workstation is try to write to a database file.. I > mean.. it is okie.. to read .. from a database.. but.. any error tracking > method.. or code.. that can find out the file is used by another machine.. > and automatically wait until the file is free.. and than write to the > database.. instead of giving me error.. when another computer is writing > data to the database.. etc.. thankz.. > >