Re: Non-updateable query issue

Based on your responses, I re-read what I had posted. It's either a grammar
and syntax issue, or a disconnect between the brain and the fingers. The
scenario I gave doesn't make sense to me either.

I'm converting a planning spread***. Each record is 100+ columns. A number
of users may have to be in the same record at one time, although not in the
same field. In an effort to avoid conflicts, I split the record into several
tables, based on the fields a particular group of users require. The tables
all relate to a master record number. When I construct a query, all tables
joined to the master, showing all the records, the query is not updateable.

I looked at other queries that I have written. Seems like I have to re-think
the relationships, or rearrange field placement in applicable tables.

Hope this clarifies things a bit.

Thanks for your responses.

Steve


"Duane Hookom" wrote:

I agree with Allen. Also, when I hear about the possibility of multiple users
editing the same record at the same time, I expect the tables are not
normalized.

--
Duane Hookom
Microsoft Access MVP


"Allen Browne" wrote:

Steve, either I have not understood you, or this is an exercise in
frustration.

You cannot prevent multi-user issues by giving separate copies of the data.
How will you ever sort them out?

Say Fred deletes record 79 from Table1, and then Betty changes the phone
number for record 79 in Table2 afterwards. You now have a deletion (which
you have presumably cached somewhere), with a more recent edit. Do you
resolve that by deleting the record in Table2? Or by restoring the record in
Table1 because there is a more recent edit? Or ...?

It seems to me that you are creating more problems than you could possibly
solve.

Anyway, here's a list of things that can cause a query to be read-only:
http://allenbrowne.com/ser-61.html
The most likely cause in your case is JOINs where neither end has a unique
index.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"sjwopg" <sjwopg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:705B9AD0-41AE-41B3-AD82-71A3BEFF20D1@xxxxxxxxxxxxxxxx
I am creating an application which will have 20+ users. In order to
minimize
errors or record locking issues, I have created three tables for each
record.
The users will enter/edit their fields without another user being in the
same
record.

Table1 has a primary key. Tables 2 & 3 have primary keys, and a foreign
key
that relates to table1.

I created a query joining Table1 to Table2 using the T1 primary to the T2
foreign, and joining Table1 to Tabel2 using the T1 primary to the T2
foreign.

This makes the query unupdateable. If I join T1 to T2, or T1 to T3, each
table is updateable. It is when I join the three tables as described
above,
that the tables become unupdateable. I've tried a number of different
scenarios, but it seems that whenever I try to join Table1 to the other
two
via the Table1 primary key, the query is unupdateable.

Any suggestions?

Thanks in advance,

Steve


.

Loading