>There seems to be a bug in Vista's file sharing that causes the ADO
>Database open command to hang if the database is open on the host
>computer.
>
>I setup a shared folder in Windows Vista giving assess to everybody.
>If I open the database on the host computer the next Windows Vista
>system to log onto the database hands on the ADO open command until
>the host PC closes the connection to the database.
>
>I wrote a simple VB program to show this bug:
>Add a module with this code:
>
>  Global MyDB As ADODB.Connection
>Sub OpenDB(ByVal DBString As String)
>  Dim FFl As Long
>  Dim NumTrys As Long
>  Dim ErrorsText As String
>  Dim I As Long
>  Dim MyResult As Long
>  Dim St As String
>    On Error GoTo DBConnectError
>    ConnectStr = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" &
>DBString ' "ApptDB.MDB"
>    Set MyDB = New ADODB.Connection ' Global Connection object.
>    With MyDB
>        .Mode = adModeShareDenyNone
>        .ConnectionTimeout = 60
>        .CommandTimeout = 60
>        .ConnectionString = ConnectStr
>        MsgBox "Before open"
>        .Open
>        MsgBox "After open"
>    End With
>    On Error GoTo 0
>    Exit Sub
>DBConnectError:
>        MsgBox Error(Err) & Chr(13) & Chr(10) & "Error number: Decimal
>" & Format(Err) & " Hexadecimal " & Hex(Err) & Chr(13) & Chr(10) &
>"Error Source: " & Err.Source & Chr(13) & Chr(10) & "Line: " &
>Format(Erl) & Chr(13) & Chr(10) & "Connection String: " & ConnectStr,
>vbCritical, "LoadDB Error"
>    End Sub
>
>Add a form with a text1 textbox and Command1 button and then add this
>code:
>
>
>Private Sub Command1_Click()
>  Dim DBString As String
>    DBString = Text1.Text
>    Call OpenDB(DBString)
>End Sub
>
>Setup a shared folder put a database in the folder and compile and
>launch on a vista computer and click the button to open the connection
>to the database.  Then on another vista machine run the program to
>open the same database.  The program will hang on the ADO open
>command.
>
>Does anyone know a work around.

> On 23 Feb 2007 15:20:26 -0800, "jwogden" <jwo***@yahoo.com> wrote:
>
> ¤ There seems to be a bug in Vista's file sharing that causes the ADO
> ¤ Database open command to hang if the database is open on the host
> ¤ computer.
> ¤
> ¤ I setup asharedfolder inWindows Vistagiving assess to everybody.
> ¤ If I open the database on the host computer the nextWindows Vista
> ¤ system to log onto the database hands on the ADO open command until
> ¤ the host PC closes the connection to the database.
> ¤
> ¤ I wrote a simple VB program to show this bug:
> ¤ Add a module with this code:
> ¤
> ¤   Global MyDB As ADODB.Connection
> ¤ Sub OpenDB(ByVal DBString As String)
> ¤   Dim FFl As Long
> ¤   Dim NumTrys As Long
> ¤   Dim ErrorsText As String
> ¤   Dim I As Long
> ¤   Dim MyResult As Long
> ¤   Dim St As String
> ¤     On Error GoTo DBConnectError
> ¤     ConnectStr = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" &
> ¤ DBString ' "ApptDB.MDB"
> ¤     Set MyDB = New ADODB.Connection ' Global Connection object.
> ¤     With MyDB
> ¤         .Mode = adModeShareDenyNone
> ¤         .ConnectionTimeout = 60
> ¤         .CommandTimeout = 60
> ¤         .ConnectionString = ConnectStr
> ¤         MsgBox "Before open"
> ¤         .Open
> ¤         MsgBox "After open"
> ¤     End With
> ¤     On Error GoTo 0
> ¤     Exit Sub
> ¤ DBConnectError:
> ¤         MsgBox Error(Err) & Chr(13) & Chr(10) & "Error number: Decimal
> ¤ " & Format(Err) & " Hexadecimal " & Hex(Err) & Chr(13) & Chr(10) &
> ¤ "Error Source: " & Err.Source & Chr(13) & Chr(10) & "Line: " &
> ¤ Format(Erl) & Chr(13) & Chr(10) & "Connection String: " & ConnectStr,
> ¤ vbCritical, "LoadDB Error"
> ¤     End Sub
> ¤
> ¤ Add a form with a text1 textbox and Command1 button and then add this
> ¤ code:
> ¤
> ¤
> ¤ Private Sub Command1_Click()
> ¤   Dim DBString As String
> ¤     DBString = Text1.Text
> ¤     Call OpenDB(DBString)
> ¤ End Sub
> ¤
> ¤ Setup asharedfolder put a database in the folder and compile and
> ¤ launch on a vista computer and click the button to open the connection
> ¤ to the database.  Then on another vista machine run the program to
> ¤ open the same database.  The program will hang on the ADO open
> ¤ command.
> ¤
> ¤ Does anyone know a work around.
>
> Are you connecting via a mapped drive letter or UNC path?
>
> Keep in mind that permissions to the resource are paramount when you are working with an Access
> database over the network. Users typically require full access to the folder where the database is
> located.
>
> Paul
> ~~~~
> Microsoft MVP (Visual Basic)

> On 27 Feb 2007 10:28:13 -0800, "jwogden" <jwo***@yahoo.com> wrote:
>
> ¤ >
> ¤ > Are you connecting via a mapped drive letter or UNC path?
> ¤ >
> ¤ > Keep in mind that permissions to the resource are paramount when you are working with an Access
> ¤ > database over the network. Users typically require full access to the folder where the database is
> ¤ > located.
> ¤ >
> ¤ > Paul
> ¤ > ~~~~
> ¤ > Microsoft MVP (Visual Basic)
> ¤
> ¤ I am using a UNC path and I have full access if the user on the host
> ¤ PC is not logged in so I must have my Access set correctly.
> ¤
>
> I'll check to see if I can repro this issue. Is this in a workgroup networking environment or are
> you in a domain?
>
> Paul
> ~~~~
> Microsoft MVP (Visual Basic)

> On 6 Mar 2007 11:44:25 -0800, janzal***@silverleaf-ent.com wrote:
>
> ¤ I have a very similar issue with Vista and asharedAccess database in
> ¤ a workgroup environment.  While not using VB, I simply am unable to
> ¤ open asharedAccess db located on a UNC physically located on a W2k
> ¤ server from recently added Vista Business machines.  All of the other
> ¤ machines can open the database concurrently, but the Vista machines
> ¤ can only open it if all other connections are closed, i.e. the db is
> ¤ not open on ANY other machine, Vista, XP or W2k.
> ¤
> ¤ Have you tried just opening the db concurrently from the Access
> ¤ interface on a Vista machine while the db is open on another machine?
> ¤ I would curious to know if you are successful...
>
> What is the error that is generated when you attempt to open thesharedAccess database concurrently
> from Vista?
>
> Paul
> ~~~~
> Microsoft MVP (Visual Basic)

> On 6 Mar 2007 11:44:25 -0800, janzal***@silverleaf-ent.com wrote:
>
> ¤ I have a very similar issue with Vista and asharedAccess database in
> ¤ a workgroup environment.  While not using VB, I simply am unable to
> ¤ open asharedAccess db located on a UNC physically located on a W2k
> ¤ server from recently added Vista Business machines.  All of the other
> ¤ machines can open the database concurrently, but the Vista machines
> ¤ can only open it if all other connections are closed, i.e. the db is
> ¤ not open on ANY other machine, Vista, XP or W2k.
> ¤
> ¤ Have you tried just opening the db concurrently from the Access
> ¤ interface on a Vista machine while the db is open on another machine?
> ¤ I would curious to know if you are successful...
>
> What is the error that is generated when you attempt to open thesharedAccess database concurrently
> from Vista?
>
> Paul
> ~~~~
> Microsoft MVP (Visual Basic)

On Mar 7, 12:53 pm, "jwogden" <jwo***@yahoo.com> wrote:
> On Mar 6, 3:20 pm, Paul Clement
>
>
>
> <UseAdddressAtEndofMess***@swspectrum.com> wrote:
> > On 6 Mar 2007 11:44:25 -0800, janzal***@silverleaf-ent.com wrote:
>
> > ¤ I have a very similar issue with Vista and asharedAccess database in
> > ¤ a workgroup environment.  While not using VB, I simply am unable to
> > ¤ open asharedAccess db located on a UNC physically located on a W2k
> > ¤ server from recently added Vista Business machines.  All of the other
> > ¤ machines can open the database concurrently, but the Vista machines
> > ¤ can only open it if all other connections are closed, i.e. the db is
> > ¤ not open on ANY other machine, Vista, XP or W2k.
> > ¤
> > ¤ Have you tried just opening the db concurrently from the Access
> > ¤ interface on a Vista machine while the db is open on another machine?
> > ¤ I would curious to know if you are successful...
>
> > What is the error that is generated when you attempt to open thesharedAccess database concurrently
> > from Vista?
>
> > Paul
> > ~~~~
> > Microsoft MVP (Visual Basic)
>
> The solution on the following thread seems to work.  It seems to be a
> bug the SMB2 file sharing.
>
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1259708&SiteID=1