This is not specific to one database. It appears my machine name is being entered into the lock file twice. Even if I open the database after first opening Access and using the open dialog to open the file exclusively. I'm waiting for my IT support to respond to my incident ticket. Sad thing is, their resolution to everything is to reimage the machine.
Darrell
--- In MS_Access_Professionals@yahoogroups.com, Crystal <strive4peace2008@...> wrote:
>
> adding on ...
>
> Darrell, try this:
>
> copy and paste the
> database to another location (then rename the original one to be a
> backup if this works). This will reset the owner properties of the
> file. With your new version of the OS, you may be a "different" user to
> the computer ... also, my advice is to NEVER store files in system
> directories like My Documents; there are issues if you have to get to
> the files from another boot drive; always create your own directory
> structures for data files.
>
>
> Happy Independence Day!
>
>
> Warm Regards,
> Crystal
> Learn Access on YouTube
> http://www.YouTube.com/LearnAccessByCrystal
>
>
> *
> (: have an awesome day :)
> *
>
>
> ________________________________
> From: Bill Mosca
>
> Darrell
>
> You don't happen to have the database open more than once, do you? I know I've done that without realizing.
>
> If you only have one open I suggest rebooting.
>
> Regards,
> Bill Mosca, Founder - MS_Access_Professionals
> http://www.thatlldoit.com
> Microsoft Office Access MVP
> https://mvp.support.microsoft.com/profile/Bill.Mosca
>
>
>
> --- "D" <embreydl@> wrote:
> >
> > Thanks John,
> >
> > There wasn't a lock file present in the folder. I was able to make one code change and when I went to make a second change, I got the "do not have exclusive access" warning.
> >
> > I also found a post referring to Adobe PDFMaker (which I have) causing a problem. I followed the instructions for that but, the problem still exists.
> >
> > I have also tried the /decompile switch without success.
> >
> >
> > Darrell
> >
> > --- In MS_Access_Professionals@yahoogroups.com, John Viescas <JohnV@> wrote:
> > >
> > > Darrell-
> > >
> > >
> > >
> > > First try: With the database closed, look in the folder where the database
> > > resides, and if there's a .laccdb file (or .ldb if older format), delete it.
> > >
> > >
> > >
> > > If you don't find the file, then come back again for another guess!
> > >
> > >
> > >
> > > John Viescas, author
> > > Microsoft Office Access 2010 Inside Out
> > > Microsoft Office Access 2007 Inside Out
> > > Building Microsoft Access Applications
> > > Microsoft Office Access 2003 Inside Out
> > > SQL Queries for Mere Mortals
> > > <http://www.viescas.com/> http://www.viescas.com/
> > >
> > > (Paris, France)
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: MS_Access_Professionals@yahoogroups.com
> > > [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of D
> > > Sent: Tuesday, July 03, 2012 5:53 PM
> > > To: MS_Access_Professionals@yahoogroups.com
> > > Subject: [MS_AccessPros] Do Not Have Exclusive Access to Database
> > >
> > >
> > >
> > >
> > >
> > > Greetings All,
> > >
> > > My work computer was updated to Windows 7 and Office 2007 last week. The first
> > > few days everything was working fine. Now, whenever I attempt to make changes in
> > > a database I get a warnig that I "do not have exclusive access to the database
> > > at this time. If you proceed to make changes, you may not be able to them
> > > later." Also, while debugging at times, I will receive "The database has been
> > > placed in a state by user 'Admin' on machine 'PCND1164N8J' that prevents it from
> > > being opened or locked." when assigning the database object to a variable or
> > > attempting to execute an action query through code. Needless to say, that
> > > machine name is my computer, this is a stand-alone copy of the database on my
> > > local drive for development, and I am the only user in the database at the time.
> > >
> > > Does anyone have any ideas as to what may be causing this behaviour?
> > >
> > > Darrell
> > >
> > >
> > >
>
>
> [Non-text portions of this message have been removed]
>
Tidak ada komentar:
Posting Komentar