Admin owns table has full permissions but can't edit a cell or add records

[gimme_this_gimme_that]

I inherited a MS Access database system where one of the tables cannot
be modified.

Through Tools->Security->User Group Permissions the table is owned by
Admin (me) and all permission checkboxes have been checked.

But I can't edit a cell or add records.

Any suggestions?

Thanks.

 

['69 Camaro]

Hi.

Through Tools->Security->User Group Permissions the table is owned by
Admin (me) and all permission checkboxes have been checked.

But I can't edit a cell or add records.

Is this a system table or a normal user-defined table? If it's a system table,
you won't be able to edit or add records directly from the table's datasheet,
nor should you. One can tell it's a system table because the "Show System
Objects" check box must be marked in the database Options dialog window in order
to see the table listed in the Database Window.

If it's a normal user-defined table, does this table reside in the current
database, or is it a linked table? If it's a linked table, check Admin's
permissions on this table in the other database file, and you'll find Admin
doesn't have "Update Data" and "Insert Data" permissions.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact info.

 

[gimme_this_gimme_that]

Thanks Camaro.

It was a linked table.

 

['69 Camaro]

You're welcome. Glad to help.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact info.

 

[gimme_this_gimme_that]

Hi Camaro,

Here was the deal.

The MS Access tabled linked to a table on a SQL Server database.

When a table in Access didn't have a primary key, the Admin's
permissions would show that he had write permissions, but actually, he
couldn't write.

The fix was to make certain a primary key was defined for the Access
tables.

 

['69 Camaro]

Hi.

The fix was to make certain a primary key was defined for the Access
tables.

Thanks for sharing this solution with us.

When a table in Access didn't have a primary key, the Admin's
permissions would show that he had write permissions, but actually, he
couldn't write.

Without the primary key (or unique index) to identify "which" record to update,
the database engine refuses to update any of them. It's safer that way, but
it's annoying because the database engine doesn't tell us why it's not doing
what we expect.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact info.

 

[John Vinson]

The MS Access tabled linked to a table on a SQL Server database.

ummm...

It would certainly have made this question a lot easier to answer if
you'ld said that.

John W. Vinson[MVP]

 

['69 Camaro]

Hi, John.

. . . if
you'ld said that.

Is that the proper grammatical contraction for Southern "if you all had said
that"? <g, d, & r -- fast!>

Gunny

 

[John Vinson]

Is that the proper grammatical contraction for Southern "if you all had said
that"? <g, d, & r -- fast!>

Waal, Ah reckon it mahht be... <g>

(grew up in Arkansas so I can say it that way if I want!)

John W. Vinson[MVP]

 

['69 Camaro]

(grew up in Arkansas so I can say it that way if I want!)

Ah, then that means you don't get the same "Y'arnt fum aroun' hee uh, ah yuh?"
responses that I get when visiting Arkansas and speaking in my best Tennessee
accent. ;-)

Gunny

 

[John Vinson]

Ah, then that means you don't get the same "Y'arnt fum aroun' hee uh, ah yuh?"
responses that I get when visiting Arkansas and speaking in my best Tennessee
accent. ;-)

It's been almost 40 years... it takes a few weeks for the accent to
come back!

John W. Vinson[MVP]