Other users unable to open DB

itchy

Utterly confused since...
Local time
Today, 23:00
Joined
Jan 25, 2001
Messages
31
Hello all,
I have a little bit of a dilema. I have an Access database which I just finished converting to Access 2000 (it was 97 before). Part of the conversion was done by the wizard and part manually. I finished my conversion and ran my tests, all works great. So I created my MDE and away we go....so I thought. It seems as if no one else but myself can be logged into the computer and be able to open the application. The database is secured and I run a number of functions at logon in order to check for certain criteria before opening the app. (You must enter a username and password to open the app.) None of these functions were altered during the conversion and seem to work fine for me and any test accounts that I create, even if I give them the group permissions as the rest of the users (as opposed to Admin). All of this works fine if I am logged on the computer. If I go to someone else's computer and try opening the app (using my own username & password), the app bugs and doesn't open. I have narrowed down the problem to the following function and have even determined the line of code where it bugs out.

Code:

Function LogOn()
On Error GoTo ErrHandler

Dim usr As String
Dim db As Database
Dim rst As Recordset
Dim i As Integer
Dim flg As Integer


Set db = CurrentDb()

***bugs out here at the next line****
Set rst = db.OpenRecordset("tblUsers")

usr = CurrentUser

flg = 0

rst.MoveFirst

While Not rst.EOF
If usr = rst!strUsername Then
If rst!numFlag = 0 Then
flg = 0
Else
flg = 1
rst.Edit
rst!numTimesLogged.Value = rst!numTimesLogged.Value + 1
rst.Update
End If
rst.MoveLast
End If
rst.MoveNext
Wend

rst.Close
Set rst = Nothing
Set db = Nothing

If flg = 0 Then
DoCmd.OpenForm "frmPasswordSetup"
Else
DoCmd.OpenForm "frmMainMenu"
End If


ExitHere:
Exit Function
ErrHandler:
Debug.Print Err, Err.Description
Resume ExitHere

End Function


Could anyone see a reason that I would have to be logged on the computer that is opening the application in order for this line to work? The thing that I find so odd is that it has nothing to do with who is logging into the application but rather who is logged on the computer. Any ideas? I am desperate!!!
 
From everything I have heard, your best bet is to remove the security before converting it and then set up the security again through 2000.

I'm going to have to do this on a number of databases at my company too, ugh!

Krysti
 

Users who are viewing this thread

Back
Top Bottom