Problem with accessing DB on a network
- Thread starter lacey
- Start date
SOS
Registered Lunatic
- Local time
- Today, 05:16
- Joined
- Aug 27, 2008
- Messages
- 3,512
SOS
Registered Lunatic
- Local time
- Today, 05:16
- Joined
- Aug 27, 2008
- Messages
- 3,512
Right.............with the exact same rimmer (look-alike) picture
Last edited:
SOS
Registered Lunatic
- Local time
- Today, 05:16
- Joined
- Aug 27, 2008
- Messages
- 3,512
That would tend to indicate that you don't have Access 2007 installed. Is that correct?
If so, you can't use an ACCDB file. If you do have it installed it looks like you'll have to do a reinstall so things are working correctly.
If so, you can't use an ACCDB file. If you do have it installed it looks like you'll have to do a reinstall so things are working correctly.
- Local time
- Today, 13:16
- Joined
- Sep 12, 2006
- Messages
- 16,075
do tools/folder options, and turn on "view file extensions"
the file is probably an .accdb, and only A2007 can open this.
you need a .mdb for A2003 to open.
the file is probably an .accdb, and only A2007 can open this.
you need a .mdb for A2003 to open.
Khalid_Afridi
Registered User.
- Local time
- Today, 16:16
- Joined
- Jan 25, 2009
- Messages
- 491
So what's the conclusion?
I told you, and I'm wonder if Microsoft Access 2007 is installed on Lacey's pc?
but the OP says that they converted the file from 2007 format to 2003 format! where is the bug
I told you, and I'm wonder if Microsoft Access 2007 is installed on Lacey's pc?
but the OP says that they converted the file from 2007 format to 2003 format! where is the bug
- Local time
- Today, 07:16
- Joined
- Feb 28, 2001
- Messages
- 30,567
Let's try to unravel something here.
Access 2007 supports TWO types of databases. The "traditional" .MDB file that has been around since Access 2.0 is an Access database application. The newer .ACCDB file type is a project file for which user-level security no longer exists. The MyAces table is "My Access Control Entries" table, which is where user-level security USED to exist.
Had the database been converted to a .MDB type, you would have been able to open it and might even still have user-level security. But as an .ACCDB type, you do not by default have the "Windows Association" that links file type .ACCDB to MS Access. Installing AC2k7 establishes all required associations when it registers itself (in the Registry, of course.) The icon you showed us is the "default" Windows icon for a file for which it doesn't have an association. It is the "I don't know what this is" type of icon.
When you get to Ac2K7, you need to "roll your own" security rules. It is possible but highly tedious. You have to start looking at "GotFocus" code and "LostFocus" code as places to dynamically enable or disable controls. You have to block out any chance of a user breaking through a startup form to get to the underlying database window and content. You have to use a lot of event code (based on button click events) to verify that users aren't doing things they shouldn't do.
I'm going through that right now. I built a prototype form with a lot of that crud already in it. Then I just copy the prototype and populated it with controls for the appropriate recordsources and rowsources, etc. Not for the faint of heart, true, but still eminently possible.
When you lose the MyAces table, you will potentially lose a lot of metadata about your database. That conversion will be more difficult than it otherwise might have been because of what else would reference MyAces implicitly.
Access 2007 supports TWO types of databases. The "traditional" .MDB file that has been around since Access 2.0 is an Access database application. The newer .ACCDB file type is a project file for which user-level security no longer exists. The MyAces table is "My Access Control Entries" table, which is where user-level security USED to exist.
Had the database been converted to a .MDB type, you would have been able to open it and might even still have user-level security. But as an .ACCDB type, you do not by default have the "Windows Association" that links file type .ACCDB to MS Access. Installing AC2k7 establishes all required associations when it registers itself (in the Registry, of course.) The icon you showed us is the "default" Windows icon for a file for which it doesn't have an association. It is the "I don't know what this is" type of icon.
When you get to Ac2K7, you need to "roll your own" security rules. It is possible but highly tedious. You have to start looking at "GotFocus" code and "LostFocus" code as places to dynamically enable or disable controls. You have to block out any chance of a user breaking through a startup form to get to the underlying database window and content. You have to use a lot of event code (based on button click events) to verify that users aren't doing things they shouldn't do.
I'm going through that right now. I built a prototype form with a lot of that crud already in it. Then I just copy the prototype and populated it with controls for the appropriate recordsources and rowsources, etc. Not for the faint of heart, true, but still eminently possible.
When you lose the MyAces table, you will potentially lose a lot of metadata about your database. That conversion will be more difficult than it otherwise might have been because of what else would reference MyAces implicitly.
Khalid_Afridi
Registered User.
- Local time
- Today, 16:16
- Joined
- Jan 25, 2009
- Messages
- 491
These all are something very new to me.
Thanks for such a comprehensive information.
Thanks for such a comprehensive information.
Thanks everyone for your replies, it looks like we got the problem cleared up...sort of :|
Our computer IT tech here on campus came and checked it out last Friday, he said there was a problem with the connection between Access 2003 and Access 2007 (what the problem was, I'm not entirely sure, I wasn't here that day.) I can open the file from my machine now.
However-there's a new problem.
I can open the DB on my machine and make changes fine. My supervisor can open the same DB on her machine and make changes just fine. But the changes we each make do not reflect on the same DB when we open it on our own PC's.
For example, I added a column in the table entitled "Progress # Quizzes", and added it to the form as well. But, when my supervisor opens it on her machine, the table is not there.
Any help is appreciated again. Thanks everyone so far!
Our computer IT tech here on campus came and checked it out last Friday, he said there was a problem with the connection between Access 2003 and Access 2007 (what the problem was, I'm not entirely sure, I wasn't here that day.) I can open the file from my machine now.
However-there's a new problem.
I can open the DB on my machine and make changes fine. My supervisor can open the same DB on her machine and make changes just fine. But the changes we each make do not reflect on the same DB when we open it on our own PC's.
For example, I added a column in the table entitled "Progress # Quizzes", and added it to the form as well. But, when my supervisor opens it on her machine, the table is not there.
Any help is appreciated again. Thanks everyone so far!
No worries, we cracked the case! It was a really simple problem, too.
My supervisor was opening the database from a folder on her desktop. She thought she had created a shortcut to that DB, but she had actually just copied it to her desktop, creating a whole new file. She had been entering the data in from there and not the original that I was accessing, that's why it wouldn't show up.
My supervisor was opening the database from a folder on her desktop. She thought she had created a shortcut to that DB, but she had actually just copied it to her desktop, creating a whole new file. She had been entering the data in from there and not the original that I was accessing, that's why it wouldn't show up.
Similar threads
