Conversion to Acc97: Query not updatable anymore

Hi,
having updated our application from Access 95 to Access 97, most of our queries have become un-updatable.

We've corrected this by removing 'DISTINCTROW' from the SQL-statement. (See Knowledge-Base-Article Q168438.)

Now, you may change any entry in a query in the spreadsheet-view of the query, and *partially* you can do so in the form which uses the query as source.

The strange thing is that on *some* computers on which our application is running it's *not* possible to edit any values in the form (in spreadsheet-view still possible); the info in the status-bar is 'This recordset is not updatable' (which corresponds to error 3326).

What could be the cause? Can anyone explain?

TIA, Christoph
mail to: christoph.beuter***@koe2.sni.de (*** to be deleted)
chrbchrbAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

BigJCommented:
Try double clicking in query design and set the recordset type to "Dynaset - inconsistent updates". This sometimes allows you to edit the returned recordset.

Sorry, can't offer an explanation as to why this might occur.

Good luck.
0
BigJCommented:
What happended when you set the recordset type to "Dynaset - inconsistent updates"?
0
chrbchrbAuthor Commented:
Adjusted points to 305
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

IanHinsonCommented:
The problem may be caused by the joins in the table relationships being down-graded from fully enforced joins to 'weak' joins.

You can check this by looking at a query which is having problems in the Query Grid.  Does the join appear with 1-'infinity' - or is it represented by a weak join?

If working to a 'back-end' database, refresh the links using the Linked Table Manager add-in.  This must be done when the front-end or back-end is converted to Acc97.

0
chrbchrbAuthor Commented:
Sorry, but we've already checked all joins, and they seem to be all correct.
We're indeed working with a back-end/front-end architecture, but have already rejoined all tables, too.
We're starting to believe that this strange behaviour is some sort of bug in Access...
0
TrygveCommented:
What happens if you try to autocreate a new form based on the recordsource for one of the forms that gives you the error ?
0
peroveCommented:
Check out properties of the query. The "Unique values" must be NO!
perove
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.