Hi, we still have some trouble running a MS Access-database on Samba. We now tried it with v.2.2.6 on RH 7.3 but still we either get no acces on the database simultanously or we run in problems with updating the database. The problem is that we make some changes on one of the clients but the changes are not visible to the other clients until they shut down the database and reopen it. We tried all lock options but there appears always one of the problems described above. If we disable oplocks in any way, only one client can open the db. We also tried to update the W2K-clients to SP3 because I read something about problems with oplocks on W2K-SP2 but nothing helped. A Google search on this problem brought up an article that MS Access has huge problems running on Samba or any other file-server-system than Windows. Has anyone ever get an Access-db running on more than 2 clients simultaneously and if yes, could you please give us some helpfull hints ? Thanks in advance. Oliver -- Oliver Krehan IT Security Assistent Actaris Hardeckstrasse 2 76185 Karlsruhe, Germany Tel: +49 721 5981 325 Fax: +49 721 5981 189 http://www.actaris.com
Not sure if this has anything to do with Samba: I try and stay away from Access but a few years ago we had similar problems with Access on a Novell server. It kept corrupting and looking at the Access documentation it seems that Access is not a multiuser database unless you program it to be. So you need to manually code all the database locking etc - an out-of-the-box one is only good for single user. HTH Noel -----Original Message----- From: Oliver Krehan [mailto:okrehan@karlsruhe.actaris.com] Sent: 18 October 2002 12:56 To: samba@lists.samba.org Subject: [Samba] MS Access and Samba Hi, we still have some trouble running a MS Access-database on Samba. We now tried it with v.2.2.6 on RH 7.3 but still we either get no acces on the database simultanously or we run in problems with updating the database. The problem is that we make some changes on one of the clients but the changes are not visible to the other clients until they shut down the database and reopen it. We tried all lock options but there appears always one of the problems described above. If we disable oplocks in any way, only one client can open the db. We also tried to update the W2K-clients to SP3 because I read something about problems with oplocks on W2K-SP2 but nothing helped. A Google search on this problem brought up an article that MS Access has huge problems running on Samba or any other file-server-system than Windows. Has anyone ever get an Access-db running on more than 2 clients simultaneously and if yes, could you please give us some helpfull hints ? Thanks in advance. Oliver -- Oliver Krehan IT Security Assistent Actaris Hardeckstrasse 2 76185 Karlsruhe, Germany Tel: +49 721 5981 325 Fax: +49 721 5981 189 http://www.actaris.com -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.394 / Virus Database: 224 - Release Date: 03/10/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.401 / Virus Database: 226 - Release Date: 09/10/2002
-----[ on 10/18/02 01:55:53 PM +0200 okrehan@karlsruhe.actaris.com wrote ]-----> Has anyone ever get an Access-db running on more than 2 clients > simultaneously and if yes, could you please give us some helpfull hints ?I have 2 Samba servers. One on a RedHat 6.2 (kernel 2.2x) and one on a RedHat7.2 server. On both of these servers I can have a database open by more than one user. User one can make a change in a table, then close the table. User two can then open the table and see the updated records. (The database is generally single user, but I did some light tests just now out of curiosity from your post.) Access/Win settings: Both clients use Access 2000 with all OfficeUpdate patches. Client 1 was Win2K + SP3 Client 2 was WinXP + SP1 Database is nothing special, tables, querys, forms, etc. Samba settings: Both servers are members of an NT domain. Neither server uses oplocks. The 7.2 server runs 2.2.1a (stock RedHat rpms) The 6.2 server runs 2.2.5 with some of the printing patches. All of the oplock settings are set to no, except for the veto oplock parameter which is unset. If you are interested in other smb.conf parameters, let me know. --Ben-- ----------------------- Ben Griffith bgriffit@email.unc.edu -----------------------
On Fri, 2002-10-18 at 13:55, Oliver Krehan wrote:> Has anyone ever get an Access-db running on more than 2 clients > simultaneously and if yes, could you please give us some helpfull hints ?Like the other poster said: It seems to depend on the application. The Access engine (JET?) is used by at least one app I know and it works fine with Samba. Can you reproduce the problem when sharing the database from NT4/W2k/XP computer? Greetings, Andreas. -- Andreas Mack <vasquez@mediales.de> mediales. GmbH http://www.mediales.de
I develop large laboratory databases with MS Access. All my back end
servers are Samba 2.2.4 on FreeBSD. The key to multi-user success lies
in these configuration points:
1. Always run the Access database application, (Forms, code,
queries, ...) on a client workstation and have the back-end data on the
server. The application container links to the shared tables on the
server.
2. Oplocks = no
3. Kernel Oplocks = no
4. Level2 Oplocks = no
5. Blocking Locks = yes
6. Locking = yes
7. Strict Locking = no
8. Share Modes = yes
Success will be improved if you follow the pessimistic locking model for
most of your data access. This means that the edited record is always
locked. You should do this regardless of whether you use Windows or
Samba on your back end server. This also applies to point number 1.
HTH,
Glenn
--
Glenn Scherb
Midwest Research Institute
425 Volker Boulevard
Kansas City, Missouri 64110
gscherb@mriresearch.org
http://www.mriresearch.org
Phone: (816)753-7600 x1806
FAX: (816)753-5359
Page: (816)990-8513
pagegscherb@mriresearch.org
-----Original Message-----
From: samba-admin@lists.samba.org [mailto:samba-admin@lists.samba.org]
On Behalf Of Oliver Krehan
Sent: Friday, October 18, 2002 6:56 AM
To: samba@lists.samba.org
Subject: [Samba] MS Access and Samba
Hi,
we still have some trouble running a MS Access-database on Samba. We now
tried it with v.2.2.6 on RH 7.3 but still we either get no acces on the
database simultanously or we run in problems with updating the database.
The problem is that we make some changes on one of the clients but the
changes are not visible to the other clients until they shut down the
database and reopen it. We tried all lock options but there appears
always
one of the problems described above. If we disable oplocks in any way,
only
one client can open the db.
We also tried to update the W2K-clients to SP3 because I read something
about problems with oplocks on W2K-SP2 but nothing helped. A Google
search
on this problem brought up an article that MS Access has huge problems
running on Samba or any other file-server-system than Windows.
Has anyone ever get an Access-db running on more than 2 clients
simultaneously and if yes, could you please give us some helpfull hints
?
Thanks in advance.
Oliver
--
Oliver Krehan
IT Security Assistent
Actaris
Hardeckstrasse 2
76185 Karlsruhe, Germany
Tel: +49 721 5981 325
Fax: +49 721 5981 189
http://www.actaris.com
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
On Fri, 18 Oct 2002, Oliver Krehan wrote:> Hi, > > we still have some trouble running a MS Access-database on Samba. We now > tried it with v.2.2.6 on RH 7.3 but still we either get no acces on the > database simultanously or we run in problems with updating the database. > The problem is that we make some changes on one of the clients but the > changes are not visible to the other clients until they shut down the > database and reopen it. We tried all lock options but there appears always > one of the problems described above. If we disable oplocks in any way, only > one client can open the db. > > We also tried to update the W2K-clients to SP3 because I read something > about problems with oplocks on W2K-SP2 but nothing helped. A Google search > on this problem brought up an article that MS Access has huge problems > running on Samba or any other file-server-system than Windows. > > Has anyone ever get an Access-db running on more than 2 clients > simultaneously and if yes, could you please give us some helpfull hints ?We're running an Access database from Samba, 3 users, with no problems. Just upgraded from Samba 2.2.5 to 2.2.6. Linux 2.4.18. Oplocks are switched off for all shares. Access 98 and 2000 from NT4 and W2k workstations. We migrated from NT4 server to Samba a few months ago. Is your database split into a backend and frontends? Every machine here has its own frontend (also located on the Samba server for convenience of upgrading) and a shared backend. Sharing frontends can be problematic, whatever server OS you're running, as Access saves various settings related to the session in this. Tim Allen
When the database is located on a Windows NT4-Server, the changes can be seen immediatly on the other 3 pcs. There is also a window popping up which announcing a sql-error but this seems to have no negative effect on the database. At a test-run under Win2k-Server the same error appears but also the changes can be seen immediatly. So in general words spoken, is the database saved on a windows machine it works as it should, is it saved on samba share no changes can be seen until the pc the changes are made on closes the database. Greetings Oliver At 15:14 18.10.2002 +0200, you wrote:>On Fri, 2002-10-18 at 13:55, Oliver Krehan wrote: > > > Has anyone ever get an Access-db running on more than 2 clients > > simultaneously and if yes, could you please give us some helpfull hints ? > >Like the other poster said: It seems to depend on the application. The >Access engine (JET?) is used by at least one app I know and it works >fine with Samba. Can you reproduce the problem when sharing the database >from NT4/W2k/XP computer? > >Greetings, >Andreas. > >-- >Andreas Mack <vasquez@mediales.de> >mediales. GmbH http://www.mediales.de > > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba-- Oliver Krehan IT Security Assistent Actaris Hardeckstrasse 2 76185 Karlsruhe, Germany Tel: +49 721 5981 325 Fax: +49 721 5981 189 http://www.actaris.com
On Fri, 2002-10-18 at 09:14, Andreas Mack wrote:> Has anyone ever get an Access-db running on more than 2 clients > simultaneously and if yes, could you please give us some helpfull hints ?I had over 25 clients connecting to an access db simultaneously. The speed was decent, but thats going to depend on you samba server. Also beware that many a time, when a certain client crashes it will usually cause data corruption/loss or a messed up db. Be very careful. Regards, Jack
On Fri, 2002-10-18 at 16:28, Oliver Krehan wrote:> When the database is located on a Windows NT4-Server, the changes can be > seen immediatly on the other 3 pcs. There is also a window popping up which > announcing a sql-error but this seems to have no negative effect on the > database. At a test-run under Win2k-Server the same error appears but also > the changes can be seen immediatly. > > So in general words spoken, is the database saved on a windows machine it > works as it should, is it saved on samba share no changes can be seen until > the pc the changes are made on closes the database.hmm so it really seems to be a samba problem. Go with the config tips of Glenn Scherb <gscherb@mriresearch.org> in this thread. Esp. oplocks seem to be a problem. As the samba docs say, they allow more aggressive caching on the client. To me it seems as NT/W2k has some detection built in for Access databases. -- Andreas Mack <vasquez@mediales.de> mediales. GmbH http://www.mediales.de