More topics

I have problem with opening my (10 years) old MDB file in Access 2010. I can open it in MS Access 2003 without any problem, but in Access 2010 I have to enter user name and password before opening. But I haven't ever set it, so I don't know it.

I just upgraded to Access 2010 from 2003. With 2003, I was able to open protected mdb files using Workgroup Administrator and joining (changing) the workgroup. This was done BEFORE opening the mdb file.

I can't do this with Access 2010 - there's no option to change a workgroup.

I scoured the internet for an answer. The closest one suggested creating a shortcut and having the target point to the Access application, then the mdb file, then use a "wrkgrp" command to point to the workgroup file (all this in one space-divided string). The answer related to Access 2007, and it doesn't work in 2010 (unless I'm doing something wrong).

I just upgraded to Access 2010 from 2003. With 2003, I was able to open protected mdb files using Workgroup Administrator and joining (changing) the workgroup. This was done BEFORE opening the mdb file.

I can't do this with Access 2010 - there's no option to change a workgroup.

The closest one suggested creating a shortcut and having the target point to the Access application, then the mdb file, then use a "wrkgrp" command to point to the workgroup file (this in one space-divided string).

I have a rather complex database in Access 2003, .mdb format. I understand the conversion to 2010 (similar to 2007) can be tedious.

I further understand that it is possible to run in .mdb format under Access 2010.

I would like to hear expert opinions ( I am most definitely NOT an Access professional), on the advisability of doing that: what features I would not be able to use, or if it is even worth leaving the coccoon of

I have an split Access database (mdb) that has just been moved to Access 2010 but kept as an mdb. In the main table there is a field that holds a Social Security Number. The new head of IT is concerned that this field has just been sitting out there on the network (rightly so) and wants to encrypt it. I have no experience with working with it at that level. Can anyone tell me if it is possible in either Access 2003 or Access 2010, mdb or accdb to do this? If so, can you tell me how? The field is not an ID field and only shows up on the form and possibly on a report

We have access 97 and we are migrating to access 2010 run-time. Is there a way to have access 2010 only take file associations over .accdb and keep .mdb associated with access97 while we convert over? I'm attempting to role access 2010 run time via group policy(Active directory) and script the whole associations thing. But the problem is every time I get the associations right, as soon as you launch access 2010 it re-registers itself for .mdb files. Very Very frustrating

I have an split Access database (mdb) that has just been moved to Access 2010 but kept as an mdb. In the main table there is a field that holds a Social Security Number. The new head of IT is concerned that this field has just been sitting out there on the network (rightly so) and wants to encrypt it.

I have no experience with working with it at that level. Can anyone tell meif it is possible in either Access 2003 or Access 2010, mdb or accdb to do this? If so, can you tell me how? The field is not an ID field and only shows up on the form and possibly on areport.

My new system will not open an MDB file from Windows Explorer when someone else has it open unless I open Access first. If the file is not open, a double-click on the file icon will open it without problems.

If the file is open by another user, my machine apparently does not open it (Access does not show up in Task Manager) but it adds my machine name to the open LDB file!

I have already tried dis-associating MDB with Access, then shutting down, and then re-associating the MDB file types with Access. It did not solve the matter.

The file is in Access 2003: I just got a new system running Windows 7 and Office 2010 today. This same issue came up previously with a co-worker with her Windows XP-Pro machine suddenly stopped opening MDBs that someone else had open unless Access was started first.