Solved

Run stored proc using 'sa' login causes write conflict

Posted on 2002-06-26
5
186 Views
Last Modified: 2010-05-02
I have a SQL Server 2000 db connected to an Access Project (.adp) front-end.

My front-end has forms with buttons that users click on to perform calculations and update data on the form. The code behind the buttons are in VB and execute stored procedures that update fields.

I make the connection in the VB code using:

myCmd.ActiveConnection = "Provider = SQLOLEDB; Data Source = server; Initial Catalog = database; User ID = sa; Password=;"

The problem I get is that everytime a user runs the code and the record is updated, the user gets the message:

Write Conflict: The record has been changed by another user since you started editing it...

Each user has their own UserName, so that is why I get the message because it has been updated by 'sa'.

How do I get around this? I don't want to connect as the user as their passwords may change, etc.

Thanks.
0
Comment
Question by:naqayya
  • 2
  • 2
5 Comments
 
LVL 5

Expert Comment

by:KMAN
ID: 7110529
You are connecting as 'sa' regardless of any other login since it is hard coded in your connection string!

Make a form where the User logs in (or registry setting, INI file, etc.), store the ID and password in a variable, then pass them to the connection string, instead of using the hard-coded 'sa' whihch is a System Administrator ID and should NOT be used to add/change/delete data.

Like:

myCmd.ActiveConnection = "Provider = SQLOLEDB; Data Source = server; Initial Catalog = database; User ID=" & strUser & ";Password=" & strPwd & ";"

Got the idea?

K
0
 

Author Comment

by:naqayya
ID: 7110585
Thanks KMAN:

My front-end doesn't take a username and password, but uses the Windows login to get the UserName and then give appropriate permissions.

I have a procedure to get the Windows UserName, but how do I get the password? I don't want to make the users login twice.

I use the following code to get the UserName:

-----------------------------------------------------------
Private Declare Function GetUserName Lib "advapi32.dll" Alias _
    "GetUserNameA" (ByVal lpBuffer As String, nSize As Long) As Long


Function o_CurrentNTUser() As String
   
   Dim strUserName As String * 25
   Dim intReturn As Integer
   
   intReturn = GetUserName(strUserName, 25)
   strUserName = Trim(Left(strUserName, InStr(1, strUserName, Chr(0)) - 1))
   o_CurrentNTUser = Trim(strUserName)

End Function
-----------------------------------------------------------

Thanks.
0
 
LVL 5

Accepted Solution

by:
KMAN earned 100 total points
ID: 7110675
I doubt there is a way to retrieve the password, like the UID.  You may try to setup a SQL Server ODBC datasource, set it to use Windows Authentication and then use a connection string like:

myCmd.ActiveConnection = "mySQLServer"


...where mySQLServer is the ODBC datasource name.

Then the individual PC's will authenticate SQLServer with the correct UID/PWDs
0
 
LVL 7

Expert Comment

by:Nitin Sontakke
ID: 7110724
A bit off the track, but i thought that the user name can also be retreived in much simpler way, in VB, as follows:

strUserName = Environ("UserName")

You can also get the domain name by Environ("UserDomain")

0
 

Author Comment

by:naqayya
ID: 7110789
Thanks NitinSontakke: yes you're right!
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Since upgrading to Office 2013 or higher installing the Smart Indenter addin will fail. This article will explain how to install it so it will work regardless of the Office version installed.
If you need to start windows update installation remotely or as a scheduled task you will find this very helpful.
As developers, we are not limited to the functions provided by the VBA language. In addition, we can call the functions that are part of the Windows operating system. These functions are part of the Windows API (Application Programming Interface). U…
Get people started with the process of using Access VBA to control Outlook using automation, Microsoft Access can control other applications. An example is the ability to programmatically talk to Microsoft Outlook. Using automation, an Access applic…

821 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question