Hi fellow Acces victims ;-)

I have recently converted three ADP's from Acc2000 to Acc2010, and I'm happy to say that I still have a few chestnut hairs left on my head (IMG:style_emoticons/default/pullhair.gif)

In access 2000 I used to rely on the UniqueTable property on the forms to protect irrelevant tables in compound queries from updating. I.E. I'd use the table that I wanted updated as the uniquetable property of the form.

However, now the UniqueTable no longer prevents me from writing in a table that is not selected as unique table!

In fact, it seems like access doesn't give a toss whether I select a unique table or not anymore. It hapilly allows me to update both tabels in a joined query.

Now, is this a bug or a feature?

I'm on SQLserver 2008 SR2

Cheers

Jock

P.S. Many users were understandably worried about control elements that used to be locked were certainly open. Ok, they should have found out in the test, but hey.....

Hi Br

Thanks for looking at my post.

The answer is no. We have been running SQLserver2008 for more than a year before the Access 2010 upgrade.

We did, however, move the SQL server instance(s) to a new server-architecture with a lot of fancy stuff that I have no knowledge of.

Jock