Problem using DAO on Server 2003

That error usually indicates that either someone else has opened the file for exclusive use, or the user opening the file does not have sufficient permissions to the folder where the file is located.

Users must have full permissions to the folder where the database is located so that the corresponding .LDB file can be created, updated and deleted.

I'm not sure what the difference is between ADO and DAO under Terminal Server. Are you opening the database for read-only access? The .LDB file is always created when an Access database is opened for write access, and deleted when the last connection to the database is closed.

OK, well that example uses the Microsoft Access object model. It isn't the same as using the DAO OpenDatabase method.

If you use OpenDatabase does the error occur? Perhaps it's an issue with using the Microsoft Access object model and not DAO.

The example you have given, tries to have exclusive access to the database and since their are other users opening the same Access database, exception occurs.
I found this code on Microsoft website, which illustrates both opening Access database exclusively and read only:

Sub OpenDatabaseX()

Dim wrkJet As Workspace
Dim dbsNorthwind As Database
Dim dbsPubs As Database
Dim dbsPubs2 As Database
Dim dbsLoop As Database
Dim prpLoop As Property

' Create Microsoft Jet Workspace object.
Set wrkJet = CreateWorkspace("", "admin", "", dbUseJet)

' Open Database object from saved Microsoft Jet database
' for exclusive use.
MsgBox "Opening Northwind..."
Set dbsNorthwind = wrkJet.OpenDatabase("Northwind.mdb", _
True)

' Open read-only Database object based on information in
' the connect string.
MsgBox "Opening pubs..."

' Note: The DSN referenced below must be set to
' use Microsoft Windows NT Authentication Mode to
' authorize user access to the Microsoft SQL Server.
Set dbsPubs = wrkJet.OpenDatabase("Publishers", _
dbDriverNoPrompt, True, _
"ODBC;DATABASE=pubs;DSN=Publishers")

' Open read-only Database object by entering only the
' missing information in the ODBC Driver Manager dialog
' box.
MsgBox "Opening second copy of pubs..."
Set dbsPubs2 = wrkJet.OpenDatabase("Publishers", _
dbDriverCompleteRequired, True, _
"ODBC;DATABASE=pubs;DSN=Publishers;")

' Enumerate the Databases collection.
For Each dbsLoop In wrkJet.Databases
Debug.Print "Database properties for " & _
dbsLoop.Name & ":"

On Error Resume Next
' Enumerate the Properties collection of each Database
' object.
For Each prpLoop In dbsLoop.Properties
If prpLoop.Name = "Connection" Then
' Property actually returns a Connection object.
Debug.Print " Connection[.Name] = " & _
dbsLoop.Connection.Name
Else
Debug.Print " " & prpLoop.Name & " = " & _
prpLoop
End If
Next prpLoop
On Error GoTo 0

Next dbsLoop

dbsNorthwind.Close
dbsPubs.Close
dbsPubs2.Close
wrkJet.Close

End Sub

Yes I noticed OpenDataBase isn't an Access object. I use OpenDatabase with DAO in other functions and it seems to run well with the same database.
So, let's face it: Our database is located on our "ordinary" cluster server (CS). Opening it the "normal way with the simple code:

Set AccessDB = New Access.Application
With AccessDB
.OpenCurrentDatabase strOverviewLedgerFullName
.DoCmd.OpenForm strForm, , , "BusinessUnit = '" & strLedgerGroup & "'"
.Visible = True
End With

works well buit takes a long time when working at a distance. Therefore we introduced the Terminal Server (TS) to speed up things. When connected to TS the code above fails.
As you probably know, when connected to TS, the Office applications run on the server and not on the user client computer. TS is "only" sending the screen picture to the client computer which means faster action.
Does this help you to understand what difference there might be betw. the two options?
I looked for a solution to open a database form or table to the screen vith DAO or ADO model but did not find any at the first glance.

Thank you Paul for not giving up!
I tested your code when connected to CS (see previous input) and it works fine. But on TS I have the same problem as before. I noticed the following:
Having executed the line
Set db = .DBEngine.OpenDatabase(strOverviewLedgerFullName, False, False)
a *.ldb file is created on the database folder.

At line
.OpenCurrentDatabase strOverviewLedgerFullName
Error 7866 "Microsoft Office Access can't open the database because it is missing, or opened exclusively by another user"
makes the fun come to an end.
Strange, isn't it? Any idea what to test next?

Paul, no success I'm afraid.

To avoid possible conflict with other code in my files, I opened a new Excel file and entered some code there to test opening a form in Northwind.mdb. Normally on a Terminal Server you can not see your own C drive. In our case we have mapped the user's C drive to "L" on TS whilst the "C" seen when connected to TS is the C on TS. Pse compare the results below:
-----------
Dim AccessDB As Access Application
-----------
Sub DisplayForm()
Dim db As DAO.Database, strDBFullName As String
Set AccessDB = New Access.Application
strDBFullName = "L:\Program Files\Microsoft Office\Office11\Samples\Northwind.mdb"
With AccessDB
.Visible = True
Set db = .DBEngine.OpenDatabase(strDBFullName, False, False)
.OpenCurrentDatabase strDBFullName
DoCmd.OpenForm "Orders"
db.Close
Set db = Nothing
End With
End Sub

At the line '.OpenCurrentDatabase strDBFullName', I get error 7866 (same as earlier)

Changing the second code line to this:
strDBFullName = "C:\Program Files\Microsoft Office\Office11\Samples\Northwind.mdb"
I get error 3051 (The Microsoft Jet Database engine cannot open the file 'see string above'. It is already opened exclusively by another user, or you need permission to view its data.)
but this time the error occurs at line
'Set db = .DBEngine.OpenDatabase(strDBFullName, False, False)'

If I first open Access I can open the database manually, although via TS-C:\ it is ReadOnly, which is expected because its C is write protected.
Is this of any help to understand the reason for the strange behaviour?
_________________
Rolf

According to my colleagues in our IT support group the read/write rights are set on the folder(s) where the database is located and it does not matter whether I connect through the Terminal Server or direct to the Cluster Server (where all or network files are saved, including the database).
And I have the right to edit the database, which I do regularly.
Remember also that I can connect and edit with DAO and ADO statements although I initially thought DAO was the problem - which was a mistake, sorry for that!
_____________________________________________
Rolf

The answer to all 6 issues is yes.
But I think the problem is solved now. I handed over the Northwind script to our admin. and he had no problem to open the database form! After having rebooted the server it works also for me and for other users I hope! So, after all it was kind of a permission issue I think, I do not know the details yet.
I appreciate your interest and patience in helping me to find a solution to my dilemma!
_______________________________________________________________________
Rolf