"This Recordset is not Updateable" when opening tables in linked .mdb

[dgunner71]

Hello all -

I have a database split into front end and back end. The front ends are stored on a individual computers while the backend is stored on a server with all tables linked.

Each time I open a linked table from my front end, the status bar says "This Record Set is not Updatable" and I cannot enter anything into the tables. I thought this would be a permissions issue on the server (within the File/Folder Properties), but I've added "Everyone" to the security with full access and still no problem.

I am able to open the back end file on my front end computer through the network - I am then able to access the database normally. (i.e. just navigate to the backend file through the network and open it on my computer).

This is a new deployment (I previously had both front end and back end on the server with users logging in via Remote Desktop). Any help or direction will be appreciated.

Program - MS Access 2010
FE Computer - Windows 7
BE Computer - Windows 7 Pro


Kind Regards.

Gunner
[imgnothumb]http://bytes.com/attachments/attachment/7178d1378040530/capture.png[/imgnothumb]

[jimatqsi]

It could be a problem of no keys on the table links. Look at one of the table links in design mode. You will get a message about how you cannot edit the design of a linked table- just click through it. Look at what is the key structure of the linked table. Is the key missing? If so, delete your link(s) and relink the table. When you are asked for the key information be sure to specify that correctly.

Let us know if that was the problem or if it needs another fix.

Jim

[zmbd]

jimatqsi:
More than likely has the right answer for you.
I've ran into this with some different DB over the years.

Usually, the best fix was to go back into the backend tables and make sure that all of them have primary keys assigned. This is one reason why I will assign a primary key to every table I create in Access!

Trying to fix this from just the front-ends will eventually lead to another headache of corrupted tables. (I learned that from an Oracle guy that was helping with another issue in the lab - he was a wizard with DBs in general.)
Once you do this, then follow jimatqsi advice about the re-linking thing. There are a ton of code snip-its out on the web to do this for you via VBA.

[dgunner71]

Thanks to all - Jimatqsi's suggestion worked like a charm! I deleted all the linked tables, re-added them and viola!

Thanks again!!

Gunner