Question Database Placed in a State

[txgeekgirl]

In Access 2010 - I am getting an error when trying to copy forms/modules into my database from another that the database has been placed in a state by user "Admin" on machine 'my machine' and cannot be opened or updated.

I saw some exchange with Bob Larson - where he said that this was because the DB wasn't split. This DB has been split from inception.

I have tried copying and renaming, pulling it off the server and copying to my local and trying to copy.paste pieces I need, and moving to another server. NOTHING

Frustrating part is that this project is in the middle stages - so to go on, I have to have these parts.

Any hints on how to stop 2010 from doing this? Anyone think these extra security measures are placed to just tick you off?

 

[DJkarl]

This happens to me anytime code changes have been made, I think Access elevates the lock permission to exclusive and won't release it until the database has been closed and re-opened. At least that always works for me, not sure if your issue is related.

 

[txgeekgirl]

I have closed and reopened several times. I started this morning from a freshly booted local machine.

I even read where all users have to be off front end and then close and reopen, compact & repair... I am running the only copy - no one else has access to this DB because it's in development - so there is no one else to kick off.

 

[txgeekgirl]

The answer is so ridiculous - I have to post!

http://www.anysitesupport.com/access-the-database-has-been-placed-opened-or-locked/

When you open a 2010 DB, as you know if you set security, you have to click Design Tools to place the login screen in design mode so you can get to the back forms, reports, modules, and macros.

Well - that sets the database into a locked exclusive state. Closing that form reopens it and allows you to edit forms, modules, reports etc.

 

[shadow9449]

The answer is so ridiculous - I have to post!

http://www.anysitesupport.com/access-the-database-has-been-placed-opened-or-locked/

When you open a 2010 DB, as you know if you set security, you have to click Design Tools to place the login screen in design mode so you can get to the back forms, reports, modules, and macros.

Well - that sets the database into a locked exclusive state. Closing that form reopens it and allows you to edit forms, modules, reports etc.

Did it work...?

SHADOW

 

[txgeekgirl]

Yes - it worked. I wouldn't post an answer that doesn't work - no one should have to look through the "answers" I got. I had to look through 2 hours worth of c r a p online to get to this one thing.

Suppose to be a well documented "BUG" - maybe they will put the fix in an SP release.

 

[shadow9449]

Yes - it worked. I wouldn't post an answer that doesn't work - no one should have to look through the "answers" I got. I had to look through 2 hours worth of c r a p online to get to this one thing.

Suppose to be a well documented "BUG" - maybe they will put the fix in an SP release.

This is nothing new. I always wonder how Microsoft can miss basic, basic things like this when they release new versions of programs. All the money they sink into something like Access 2003 and no one "noticed" that tab controls flicker and it took them till service pack 3 in 2007 to resolve it?

Come on...

SHADOW

 

[txgeekgirl]

This is nothing new. I always wonder how Microsoft can miss basic, basic things like this when they release new versions of programs. All the money they sink into something like Access 2003 and no one "noticed" that tab controls flicker and it took them till service pack 3 in 2007 to resolve it?

Come on...

SHADOW

I know - and you and I both know they are hard at work on Office 2012 and don't care much about "fixing" issues not taken care of for 2010.

I can say that we are bound to Microsoft for most in-house DB projects (about 65%) and therefore I wish Microsoft would A) slow down on releases every 2-3 years, B) make everything backwards compatible, and C) let DBAs beta their releases for real functionality.

 

[shadow9449]

I know - and you and I both know they are hard at work on Office 2012 and don't care much about "fixing" issues not taken care of for 2010.

Correct. Access 2003 was not stable until SP3 (!!) which was released AFTER Access 2007.

I can say that we are bound to Microsoft for most in-house DB projects (about 65%) and therefore I wish Microsoft would A) slow down on releases every 2-3 years, B) make everything backwards compatible, and C) let DBAs beta their releases for real functionality.

I think that the time between releases is actually quite reasonable. 2007, 2010, the next one possibly 2014 or 2015? There definitely is enough beta testing but it really beats me why BASIC things are messed up in each new release. The list of basic bugs each time consists of things that anyone can find in a few minutes, not complex and unusual scenarios.

What do you mean by backwards compatible? I can run an Access 2000 database using Access 2010? What aspect (other than being able to modify toolbars) is not backward compatible?

SHADOW

 

[txgeekgirl]

We have had minor issues in 2003 to 2010 compatiblity and had one developing machine in 2007 which had a lot of issues in 2007-2010 compatibility.

Our Recordsets had issues - we had to modify the reference library. Also, we had to code around automatic emails.

I still have 4 DBs to "play" with in 2010, modify and then update to the newer server. Those are "someday when I get time" issues though.

 

[shadow9449]

We have had minor issues in 2003 to 2010 compatiblity and had one developing machine in 2007 which had a lot of issues in 2007-2010 compatibility.

Our Recordsets had issues - we had to modify the reference library. Also, we had to code around automatic emails.

I still have 4 DBs to "play" with in 2010, modify and then update to the newer server. Those are "someday when I get time" issues though.

That's odd...I've never had to make any changes.

With regard to the automatic emails, I'll guess you had a reference to Outlook. I always use late binding because of that problem.

SHADOW

 

[shadow9449]

Ohhhh....I thought of an example.

When Access 2007 was released, the ability to export a report to Excel was disabled. This functionality was supposedly fixed (I can't get it to work) in SP2.

Access 2007 was released at the beginning of 2007. SP2 at the beginning of 2009. That means that I paid all that money to Microsoft to be lacking an important function that worked perfectly in the preceding versions for 2 1/2 years. They KNEW they knocked out the functionality before releasing it. Fixing it after 2 1/2 years is NOT acceptable.

SHADOW

 

[txgeekgirl]

Ohhhh....I thought of an example.

When Access 2007 was released, the ability to export a report to Excel was disabled. This functionality was supposedly fixed (I can't get it to work) in SP2.

Access 2007 was released at the beginning of 2007. SP2 at the beginning of 2009. That means that I paid all that money to Microsoft to be lacking an important function that worked perfectly in the preceding versions for 2 1/2 years. They KNEW they knocked out the functionality before releasing it. Fixing it after 2 1/2 years is NOT acceptable.

SHADOW

We have 7 macros in play in Excel across several programs. Those written in 2007 all had to be re-written for 2010. The only issue I still have in 2010 from the 2003 migration is that the Personal workbook wants to have to be open to run macros. My SEUs start putting data in the cells and save and corrupts the Personal WB.

We do a lot of automation in calling other servers, running PS scripts, Importing and exporting to other machines, DBs and programs. Some of those calls weren't happy migrations.