Secured database moved to different server. Can't open.

[SoftwareSavvy]

My client's secured database was moved to a different server because the old server was dying, and now it won't open and gives a "conversion" error message described in the "P.S." below.

The workgroup file was copied to the new server and we joined the new workgroup. But the database still wouldn't open until the IS guy did some kind of "share" command from the new server that pointed to the old server. After that, it worked.

The old server is dying, however, and will have to be tossed pretty soon. What can I do to make the database work without the old server?


P.S. The error message that comes up when the database won't open seems unrelated to anything:

"This database is in an unexpected state; MS Access can't open it.

This database has been converted from a prior version of MS Access by using the DAOCompactDatabase method instead of the convert database command on the tools menu (database utilities submenu). This has left the database in a partially-converted state.

If you have a copy of the database in its original format, use the convert database command on the tools menu (database utilites submenu) to convert it. If the original database is no longer available, create a new database, and import the tables and queries to preserve your data. Your other database objects can't be recovered."

NOTE: This database has been converted from 97 to 2000, but I don't know why it would work on the old server, but not the new.

Thanks for your help!

Deborah Straub, Certified Microsoft Office Master
925-676-5503
deb@SoftwareSavvy.biz

http://www.SoftwareSavvy.biz

 

[VBslammer]

Here's a link that should point you in the right direction:

http://dbforums.com/showthread.php?threadid=300118

VBSlammer

 

[JeremyNYC]

VBSlammer,

Are you saying you think the problem is with corruption? It's not a corruption issue, as it works once the files (appear to be/are) where they need to be.

Jeremy =============
Jeremy Wallace

http://www.AlphaBetCityDataworks.com

Designing, Developing, and Deploying Access databases since 1995.

 

[JeremyNYC]

SoftwareSavvy,

The issue is that you were pointed to the wrong place for a little while and your network person gave you a temporary fix.

I'm in process of putting together another short article on this subject that will go up on my website (see my sig, below). Most of this is what will go on that site, though I've just written it in response to your posting.

You should talk to your network person and find out where the files will ultimately be residing and then go through and build a batch file and shortcut as outlined below. It will make your life a lot easier if you get in the habit of having users open your databases in this manner.

Jeremy
======================

I would suggest that you take a little bit of time to institute a new way of opening databases. It will sound a little complex at first, but it will make a very big difference in giving you more control over how your users open your databases and how your databases are secured.

The first step is to have all of your users join the default workgroup, the one that came with Access. This will mean that people don't have to log in every time they use access, only when they want to use a secured database. If you have any users who ever need to open any other database than one you've secured, they will be mighty happy about this. It will also make it easier for you to create little databases for testing.

The next step is to create a batch file for each secured database you or your users use. Don't be intimidated by this step. A batch file is just a text file with a name that ends in ".bat". Use notepad to make this file.

The batch file can be used to do some cool tricks. My typical batch file does a complete installation if needed, and only starts the database, if it's already been installed on the user's machine. For now, I'll just look at making a batch file to start the database--it's quite simple.

You batch file, for now, can have just one line in it. The line will be in this format:
"Path and filename for MSAccess.exe" "Path and filename for your database" /wrkgrp "Path and filename for your workgroup"
Here's a typical one-liner for one of my databases:
"C:\Program Files\Microsoft Office\Office10\msaccess.exe"
"C:\BrXp\Prdction\BrXpFE.mdb"
/wrkgrp "T:\BrXp.mdw"

I've put each element on it's own line to make it easier to read, but in your batch file all three of these lines will be combined into a single, very long, line.

This batch file will go on the server, in the same location as your database's back end.

The final step is to make a shortcut that will go on the user's desktop. This shortcut is even simpler than the batch file. The shortcut, as a matter of fact, points straight to the batch file. Here's the Target line from the shortcut that points to the batch file above:
T:\BRServer.bat

The reason to do this, instead of just giving the user a shortcut that opens the database with the right mdw, is that this way, if you need to keep people from opening new copies of the database, all you have to do is rename that batch file. Sure, if they poke around a whole lot they'll be able to do it. This is not a security measure. But it is an awfully big convenience.

===================

I'll be adding a longer article, too, on how to make a batch file that does the installation routine for you. It's _very_ handy. =============
Jeremy Wallace

http://www.AlphaBetCityDataworks.com

Designing, Developing, and Deploying Access databases since 1995.

 

[RacerGirl117]

I had this problem too when our server got converted and moved. Turned out that on the old server the database was being mapped to a nonexistant drive. We actually lost quite a bit of data from that.

I like the batch file idea. I'll have to try that sometime. But Jeremy, what do you mean by "installation routine"? Jessica Morgan
Fire Fighter Sales & Service Co.
Pittsburgh, PA

 

[JeremyNYC]

Jessica,

I'll put together a longer post soon (though I did it once before and can't seem to find it) about this but...

The installation routine builds the necessary directories, copies an icon, a splash screen bmp, and the database to the user's PC, installs a dll, and starts the database. And it manages to do this in such a way that it doesn't bomb out if any of those files are already there.

Jeremy

PS: If you happen to go poking around and find that old quote of mine (it's on one of the access forums here), I'd love it if you could send me a url to get back there!! =============
Jeremy Wallace

http://www.AlphaBetCityDataworks.com

Designing, Developing, and Deploying Access databases since 1995.