Another user logged in?

[Ruth Isaacs]

Hello All

I have a split frontend/backend mdb, with the backend on a fileserver and
frontends on each of 5 PCs. For some reason, from this morning whenever
anyone opens the frontend on any of the PCs a message comes up saying that
"The Microsoft Jet database engine stopped because you and another user are
attempting to change the same data at the same time". This happens even when
4 of the 5 PCs are switched off. The fileserver does not have Office
installed, and certainly does not have the backend open. I have checked that
the ldb file is not open before opening the mdb on a PC.

I do have the ShowUserRosterMultipleUsers module below, and, with just one
PC switched on and logged into the mdb, doing ctrl-G and entering
ShowUserRosterMultipleUsers seems to suggest that the one user on the one PC
is looged in 3 times - I get 3 lines each showing the name of the PC and the
same login name: the 'connected' value is shown as True, and the 'suspect
state' is shown as Null - on all 3 lines.

I don't get this. After clicking OK on the "The Microsoft Jet database
engine stopped ... " message I can log in OK, seemingly unaffected by
whatever is going on, but it's very unsettling!!

Hope someone can help.
Many thanks
Les

Option Compare Database
Option Explicit

Sub ShowUserRosterMultipleUsers()
Dim cn As New ADODB.Connection
Dim cn2 As New ADODB.Connection
Dim rs As New ADODB.Recordset
Dim i, j As Long

cn.Provider = "Microsoft.Jet.OLEDB.4.0"
cn.Open "Data Source=C:\Payedoc programmes\newfrontend.mdb"

cn2.Open "Provider=Microsoft.Jet.OLEDB.4.0;" _
& "Data Source=C:\Payedoc programmes\newfrontend.mdb"

' The user roster is exposed as a provider-specific schema rowset
' in the Jet 4 OLE DB provider. You have to use a GUID to
' reference the schema, as provider-specific schemas are not
' listed in ADO's type library for schema rowsets

Set rs = cn.OpenSchema(adSchemaProviderSpecific, _
, "{947bb102-5d43-11d1-bdbf-00c04fb92675}")

'Output the list of all users in the current database.

Debug.Print rs.Fields(0).name, "", rs.Fields(1).name, _
"", rs.Fields(2).name, rs.Fields(3).name

While Not rs.EOF
Debug.Print rs.Fields(0), rs.Fields(1), _
rs.Fields(2), rs.Fields(3)
rs.MoveNext
Wend

End Sub

[Joan Wild]

I would get everyone out, verify at that point that there is no ldb file in
the backend's folder, and then open the backend and run compact and repair
(after backing it up).

--
Joan Wild
Microsoft Access MVP
"Ruth Isaacs" <les...@gppayroll.org.uk> wrote in message
news:O18rS0kI...@TK2MSFTNGP02.phx.gbl...