Hvad kan en Access-database holde til?

En access database kan ikke klare meget mere end 60 samtilige bruger tilslutningen!

Du bør nok opgradere til MySQL.. kender dog ikke nogle sider omkring det, men en access database er for lidt til dine behov =)

Take a look at this question!
http://www.eksperten.dk/spm/209672

in particular teh comment 11/05-2002 10:37:20 :o)

Oki, tak for svarene. Tjekker lige links!

Hvis andre har kommentarer eller svar, så kom venligst med dem.

Så bliver jeg så glad :o)

I just had a look at your site and it does seem to be a bit slow!
If you read the comments I make in the other question http://www.eksperten.dk/spm/209672 you will see that I suggest that as soon as you have read the database then the connection should be closed!
Now I have NOT had a GOOD look at your site but I cant see ANY place where users can WRITE to your Access database, so therefore you are only reading data from the datbase and this should be NO problem!

Try closing the connect once you have read your data and see if it helps!
Also try compacting your database (can only be done when there are no users)

Nice site :o)

I can see that you do have a forum where there will be updates!
A simple solution was to actually have two databases, One for the forum and another for the read only topics!

Kan det ikke trække databasen ned, hvis mange læser fra den?

Forummet, databasen og poll'en er 3 forskellige databaser, så på den måde har jeg sikret mig.

men kan det ikke være databasens skyld, at den er langsom, når folk kun læser fra den?

Normally read operations DO NOT put so much load on the database as writes do. When you say "3 forskellige databaser" do you mean three .mdb files or 3 tables in one mdb file? There is a BIG difference!

An Access database tends to "GROW" when write operations take place, this is not normally the case when only read operations take place.

Have you any idea WHICH database (if it is three databases and not tables) which is slow?
You should always close connections as soon as possible, also when users only read from the database. If connections do not get closed then resources are NOT being freed!

My advice is close connection AS SOON AS THE OPERATION (READ OR WRITE) IS FINISHED!

Jeg mener 3 forskellige mdb-filer, og jeg er næsten helt sikker på, at det databasen, hvor nyheden skal loades fra, der er langsom - er dog ikke helt sikker. Folk skriver dog sjældent til databasen, og hvis det holder stik, at det ikke trækker ned at læse fra den, burde det ikke være den.

Hvordan sørger man for at "close" connections?

Here is an example in Visual Basic but ist smuch the same in other languages. Its the last few lines that are important!

Public Sub OpenX()

  Dim Cnxn As ADODB.Connection
  Dim rstEmployees As ADODB.Recordset
  Dim strCnxn As String
  Dim strSQLEmployees As String
  Dim varDate As Variant

  ' Open connection
  strCnxn = "Provider=sqloledb;Data Source=MyServer;Initial Catalog=Pubs;Integrated Security=SSPI; "
  Set Cnxn = New ADODB.Connection
  Cnxn.Open strCnxn
 
  ' Open employee table
  Set rstEmployees = New ADODB.Recordset
  strSQLEmployees = "employee"
  rstEmployees.Open strSQLEmployees, Cnxn, adOpenKeyset, adLockOptimistic, adCmdTable

  ' Assign the first employee record's hire date
  ' to a variable, then change the hire date
  varDate = rstEmployees!hire_date
  Debug.Print "Original data"
  Debug.Print "  Name - Hire Date"
  Debug.Print "  " & rstEmployees!fname & " " & _
      rstEmployees!lname & " - " & rstEmployees!hire_date
  rstEmployees!hire_date = #1/1/1900#
  rstEmployees.Update
  Debug.Print "Changed data"
  Debug.Print "  Name - Hire Date"
  Debug.Print "  " & rstEmployees!fname & " " & _
      rstEmployees!lname & " - " & rstEmployees!hire_date

  ' Requery Recordset and reset the hire date
  rstEmployees.Requery
  rstEmployees!hire_date = varDate
  rstEmployees.Update
  Debug.Print "Data after reset"
  Debug.Print "  Name - Hire Date"
  Debug.Print "  " & rstEmployees!fname & " " & _
      rstEmployees!lname & " - " & rstEmployees!hire_date

  rstEmployees.Close
  Cnxn.Close
  Set rstEmployees = Nothing
  Set Cnxn = Nothing

End Sub
'EndOpenVB

The example is for the connection and recordset objects.