Linked table makes DB read-only

[groleau]

Read-only access database has a linked table that is actually
an ODBC connection to another Access DB.

Every time we try to update the "real one," if anyone is
using the linked version, it makes the master also read-only
and we can't update it.

Is there a way around this?

--
Wes Groleau

http://www.Parkview.com/

 

[PHV]

Does the linked table recognize the Primary Key ?

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[groleau]

There is no primary key.

The master has VBA and macros that load data from
accounting reports into numerous tables, then with various joins and other massaging, create one table serving
payment info.

The users only need the final table, so I made it a linked
table.

The closest thing to a unique field would be invoice
number, but even that is not unique because an invoice
can be paid in error, then "un-paid" and repaid correctly.

All three of thsoe would have the same invoice number.

What I find so weird is that if I let the users into the master, Access will allow me to add records while
they are looking at it, but if they are looking at the data
through ODBC, I am not allowed to update it.

--
Wes Groleau

http://www.Parkview.com/

 

[PHV]

For me, never ever link table without PK !

 

[groleau]

For me, never ever link table without PK !"

Why? This is caused only by not having a primary key?

There is no field that is eligible to be a primary key.

--
Wes Groleau

http://www.Parkview.com/

 

[PHV]

Have you tried a simple AutoNumber field ?

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[groleau]

Well, I might add one and see what happens.
Still makes no sense to me, though.

--
Wes Groleau

http://www.Parkview.com/

 

[bubba100]

PHV is correct

 

[groleau]

I added an autonumber field and made it a primary key (even though it is used by nothing).

Unfortunately, Access assumed that when loading the table, it had to obtain values for that field from the other tables from which the table was assembled. Consequently, the update process failed, conmplaining that the source tables did not contain any such field.

Took that field out, and again the update works--IF no users are looking at their read-only back-end (or is that the front-end?)

--
Wes Groleau

http://www.Parkview.com/