Conversion to Acc97: Query not updatable anymore

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*** (*** to be deleted)
Who is Participating?
peroveConnect With a Mentor Commented:
Check out properties of the query. The "Unique values" must be NO!
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.
What happended when you set the recordset type to "Dynaset - inconsistent updates"?
Easily Design & Build Your Next Website

Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store. Get started with your free trial today, and when ready, take 10% off your first purchase with offer code 'EXPERTS'.

chrbchrbAuthor Commented:
Adjusted points to 305
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.

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...
What happens if you try to autocreate a new form based on the recordsource for one of the forms that gives you the error ?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.