Question "Converting" split Access 2003 *.mdb to 2010 *.mdb

[sjl]

Hello,
I've been given notice that I need to get my Access 2003 (split) database working as an Access 2010 database. There are 20 folks who have access to a copy of this database, on their local hard drive (the back-end sits on a server).

I could only find this simple step for converting from 2003 to 2010:

Within Access 2010:
1. Open the old database
2. Select File (chose file)
3. Save & Publish
4. Save Database As.... Choose "Access Database"

Problem: My database is passworded, so I don't know how I can get it pulled into Access 2010 (in order to Save & Publish it as a 2010 dbase).

Do I have to open a blank DB in Access 2010, and pull everything over?


Any tips appreciated,
sjl

 

[boblarson]

You may not need to convert the backend unless you are going to use some of the newer table features (data macros, attachment fields, etc.). But to do so I would create a new 2010 file and then IMPORT everything in.

Same goes for the frontend as far as converting. I would create a new 2010 ACCDB file and then IMPORT everything in from the old. It seems to work better that way.

As for password, you may have to remove it in order to import. If you are using Access security (and not just a database password) you will not be able to use that with the new 2007/2010 file structure and would need to continue using the old mdb file structure, which means you can't use some of the newer features.

 

[sjl]

Thanks Bob for your reply. As usual, it was insightful.

I did yank off the user-level security from a copy of my ver 2003 db so that I could import all of it into a blank 2010 db. It seems to be performing well in my testing (save from the *.snp reports not opening, as I read that they would not).

However, I'm still not sure (after quite a lot of reading of this and that) how I can get read-only access (for most of the users)s...short of going with SQL Server back-end.

Is a SQL back-end the only way to getting read-only access (of a split db) if one goes converts totally to a version 2010 *.accdb ?

sjl

 

[boblarson]

So what are you trying to make read only? For people using the forms through the database or people connecting up in some other way? The first method is easy as you can set your forms to AllowEdits NO. But there really is no way to protect the tables if they connect from some other means or access tables or queries directly.

 

[sjl]

I actually have a number of fields that I do have set up with AllowEdits NO, because only I am to add/delete/amend them.

Then there are 2 folks who need to key data into other fields as it comes available, so for most of the fields I cannot set AllowEdits=NO. Under ver 2003, it was convenient to assign these 2 folks Full Data use so they can edit/add to most of the data fields (those that have AllowEdits=Yes).

The majority of folks we don't want to be able to change anything. Under 2003, I conveniently assigned them Read-only use so they can just view the data (and view canned reports) but not mess up the data in the Forms.

So, if I don't have the user-level security in 2010, I'm needing to come up with another way to create the above scenario I just described. Maybe making a Protected Access Database, with compiled VBA *.accde (like old *.mde) for read-only users, and then a regular *.accdb for those who need full data use? A bit of mickey mouse whenever I need to deploy new forms and functionality....

 

[boblarson]

I think you may not realize that an ACCDE doesn't make the data read only. You could end up having to set your forms' AllowEdits property based on a table which has the users listed who can edit and then locks out all others based on their computer login. or something else.