Cannot open .mdb file by double click when another user has opened
in [General]
|
Prev: wcv
Next: Disable Keyboard Input
From: joelgeraldine on 17 Mar 2010 09:23 fghjkklll "david" <david(a)nospam.au> a �crit dans le message de groupe de discussion : OyNvB5NuKHA.3408(a)TK2MSFTNGP06.phx.gbl... > Underneath, an OPLOCKS problem. First user has > automatic opportunistic locking from Server 2008, and > must release the database back to the server before > it can be opened. Probably a timing issue here. > > On top, a DDE problem. Shell is probably using DDE > to tell Access which file to open. It fails with no error > message (a characteristic of DDE). Probably a timing issue. > >> I heard that new server is not in the same domain than users are, >> may be this is the reason? > > That would make the network slower. It may cause timing issues. > > > If this is right, possible solution would be to disable Opportunistic > Locking on the Server and/or on the Workstations. > > Easier solution would be to open Access first, then open the > database from Access menu. > > (david) > > > "Peter" <Peter(a)discussions.microsoft.com> wrote in message > news:7C9CC5A1-F9B3-4021-88CE-0AF2E0DFF97B(a)microsoft.com... >> Hi, >> >> Today i get information that our local file server was moved to windows >> Server 2008 and also our .mdb files were moved. We have .mdb database in >> our >> team and we could edit it at one time. >> After this server migration we cannot open this .mdb file from shared >> drive >> at one time. Now we have situation if one user has already opened by >> double >> clicking this .mdb file, another user cannot open the same .mdb file by >> double clicking this file and don't receive any error messages. >> But very interesting is that if second person will open Access first and >> after that will open .mdb file through "Open" menu from shared network >> drive, >> it is accessible. >> >> What may be the reason of such strange situation? >> >> I heard that new server is not in the same domain than users are, may be >> this is the reason? >> >> Peeter > > |