Frustrated - Exclusive lock preventing converting mdb 2003 to 2007

[Guest]

I am attempting to convert several mdb's developed in 2003 to 2007. The
conversion process will not start due to the fact the Access 2007 opened the
databases in exclusive mode. I have made multiple attempts at opening the
database without exclusive mode, but I still have the issue. Has any found a
way to open a database in 2007 without an exclusive hold on it so it can be
converted to 2007. This is getting very frustrating.

Thanks

 

[Guest]

Are you opening the DB's by double-clicking on them?
If so, try opening them from within Access...

Steve

 

[Guest]

Are you opening the DB's by double-clicking on them?
If so, try opening them from within Access...

Steve

 

[Douglas J. Steele]

You could always try creating a new database in 2007 and importing
everything from the 2003 database into it.

 

[Guest]

I have opened the database from within Access and selected the "OPEN" option
and still Access 2007 opens it as exclusive. I have created an empty
database with 2007 and imported the database - 2007 did not convert the
database but made the new one a 2003 version database. I am running on Vista
and I am wondering if Access 2007 running under Vista has issues. Every
database that I open - regardless of the method - double clicking or through
Access, opens the database in exclusive mode. This is going to be an issue
for those who what to share the database.

I am running out of options, unless there is some option setting that will
turn exclusive off. I do have my Access 2007 settings to also create and use
a database in shared mode with locking at the edit row level. Dispite this,
Access 2007 is ignoring my settings and doing what it thinks is correct,
hence the frustration.

Anyone who can shed some light on this, it would be appreciated.

Thanks
--
Robert

You could always try creating a new database in 2007 and importing
everything from the 2003 database into it.

 

[Pete D.]

2007 open exclusive is an option, might see if it turned on.

I have opened the database from within Access and selected the "OPEN"
option
and still Access 2007 opens it as exclusive. I have created an empty
database with 2007 and imported the database - 2007 did not convert the
database but made the new one a 2003 version database. I am running on
Vista
and I am wondering if Access 2007 running under Vista has issues. Every
database that I open - regardless of the method - double clicking or
through
Access, opens the database in exclusive mode. This is going to be an
issue
for those who what to share the database.

I am running out of options, unless there is some option setting that will
turn exclusive off. I do have my Access 2007 settings to also create and
use
a database in shared mode with locking at the edit row level. Dispite
this,
Access 2007 is ignoring my settings and doing what it thinks is correct,
hence the frustration.

Anyone who can shed some light on this, it would be appreciated.

Thanks

 

[Guest]

I rechecked my Access 2007 settings and under the Advance settings I have my
default set to "shared" with the record locking at "edited" This why I am
not sure what 2007 is doing - since it is ignoring the setting I have in
place and using something either set in the database or their is an issue
with 2007.

I am not the only one experiencing this. I have read several other
questions regarding this here. No answer yet that addressed the issue.

 

[Pete D.]

Try this, don't know if it is the same problem but I'll keep looking. Pete
D.
http://support.microsoft.com/kb/824278/en-us

 

[Pete D.]

One other thought, try converting it to one version lower and then bring it
to 2007. Also have you tried opening it with the decompile option once,
recompile and convert.

 

[Guest]

Pete,

Thanks for the suggestion, I will try it. I am moving Access 2007 to
another computer with XP Pro to see if the issue is between Access 2007 and
Vista.

I will let you know.

Thanks

 

[Pete D.]

Thanks, this one is interesting. I'll be watching to see if you get a
solution. Pete D.