Concurrent access problem

  • Thread starter Thread starter cctiang
  • Start date Start date
C

cctiang

Hi..I have develop an application with MS Access as my
database. I have the problem when come to the concurrent
access by more than 1 user. The transaction no. will
duplicate, as the result will affect my data integrity.
How can I lock the database when 1 user is doing the
updating while waiting for another request to coming in?

Thank you for your help.
 
Hi,

Have the users open the database in exclusive mode, see:
ACC2000: How to Use Command-Line Switches in Microsoft Access
http://support.microsoft.com/default.aspx?scid=kb;en-us;209207

Example:
c:\Program Files\Microsoft Office\Office\msaccess.exe Northwind.mdb /Excl
/X Add Products

I hope this helps! If you have additional questions on this topic, please
respond back to this posting.


Regards,

Eric Butts
Microsoft Access Support
(e-mail address removed)
"Microsoft Security Announcement: Have you installed the patch for
Microsoft Security Bulletin MS03-026? If not Microsoft strongly advises
you to review the information at the following link regarding Microsoft
Security Bulletin MS03-026
<http://www.microsoft.com/security/security_bulletins/ms03-026.asp> and/or
to visit Windows Update at <http://windowsupdate.microsoft.com/> to install
the patch. Running the SCAN program from the Windows Update site will help
to insure you are current with all security patches, not just MS03-026."

This posting is provided "AS IS" with no warranties, and confers no rights

--------------------
| Content-Class: urn:content-classes:message
| From: "(e-mail address removed)" <[email protected]>
| Sender: "(e-mail address removed)" <[email protected]>
| Subject: Concurrent access problem
| Date: Mon, 12 Apr 2004 02:03:22 -0700
| Lines: 8
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcQgbQF6hmmlK7UOSk2JzWQtfwZyiQ==
| Newsgroups: microsoft.public.access.security
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.access.security:9900
| NNTP-Posting-Host: tk2msftngxa12.phx.gbl 10.40.1.164
| X-Tomcat-NG: microsoft.public.access.security
|
| Hi..I have develop an application with MS Access as my
| database. I have the problem when come to the concurrent
| access by more than 1 user. The transaction no. will
| duplicate, as the result will affect my data integrity.
| How can I lock the database when 1 user is doing the
| updating while waiting for another request to coming in?
|
| Thank you for your help.
|
 
Hi,

Thank you for your reply. Actually my database is in a
shared access multi user environment. Each time when
there is more than 1 user posting their requests to the
database to perform updating to the same table, the
transaction no. will duplicate. How can I make sure the
database is lock for 1 user while waiting another user to
perform the subsequence updating? I suppose once the
first process of updating completed; the database will
release the access to the following user to perform the
same updating to the same table by assigning different
transaction no.

Thank you for your help.

-----Original Message-----
Hi,

Have the users open the database in exclusive mode, see:
ACC2000: How to Use Command-Line Switches in Microsoft Access
us;209207

Example:
c:\Program Files\Microsoft Office\Office\msaccess.exe Northwind.mdb /Excl
/X Add Products

I hope this helps! If you have additional questions on this topic, please
respond back to this posting.


Regards,

Eric Butts
Microsoft Access Support
(e-mail address removed)
"Microsoft Security Announcement: Have you installed the patch for
Microsoft Security Bulletin MS03-026? If not Microsoft strongly advises
you to review the information at the following link regarding Microsoft
Security Bulletin MS03-026
<http://www.microsoft.com/security/security_bulletins/ms0 3-026.asp> and/or
to visit Windows Update at
Click to expand...
the patch. Running the SCAN program from the Windows Update site will help
to insure you are current with all security patches, not just MS03-026."

This posting is provided "AS IS" with no warranties, and confers no rights
Click to expand...
 
It all depends on how you are determining the next available transaction
number. If you are using an autonumber, you should not get duplicates -
barring Access bugs, of course! But if you are "rolling your own", you will
certainly get duplicates, unless you handle the multiuser concurrency issues
properly.

So, how are you getting that number?

HTH,
TC
(off soon for the day)
 
Thank you for your reply. I have my own rolling number.
So, how can I handle the multiuser concurrency issue?
 
sorry for the late reply..I'm using VB6 as my development
tools and Access as my database. Anywhere thank you for
all your answer..I'm able to solve my problem now.
 
Back
Top