it should all be so simple

[anewor]

Ok, apologies if I don't explain this as clearly as I possibly should. The background to this problem relates to 2 tables which I shall creatively call 'x' and 'y'. Yesterday, I renamed table X to be called Z and table Y was renamed X. (table y was an updated via cutnpaste version of the old table x so had same field names).

So, about 95% of my queries were based on the old X table, so I went through the long task of manually updating their data source to the new X table.

However, quite a few of my queries are now throwing up the message "This Recordset is not updateable" whenever i try to edit a record and they also won't allow me to enter new records.

I'm sure its something really easy that i've neglected to do, but i've been staring at my screen too long to see it.

Any suggestions???

 

[Pat Hartman]

If you had the auto-correct features turned on before you started renaming, that may have caused behind the scene changes that you are not aware of.

 

[anewor]

Nope autocorrect features were not on. I just can't work out why this is problem is not occurring across all the queries. But I guess when I (or anyone who wants to help) figures out what I've done (or not done as the case may be) that answer should also become apparent.

: )

 

[Modesty_Blaze]

Have you tried...

...to re-create one query that is not big or complicated, I mean from ground up?

It might not give explanation for your problem but it just as well, might solve it!