Page 1 of 1. Recordset type: Dynaset Inconsistent Update 4. Dynaset Inconsistent Updates 5. Dynaset Inconsistent Updates 6. Dynaset Inconsistent Update 8. Dynaset Inconsistent Updates 9. If you're only going to display the results of a particular query, snapshot is appropriate; if you're going to update, then you need a dynaset; only if normal default dynaset doesn't work would you ever need to specify inconsistent updates.
My experience with using a tab control for application navigation, which I tried as an experiment when the tab control first came out, was this: It took at least twice as long to develop as a traditional multi- form application. When I asked for user feedback on ease of use after I delivered it, they "thought it was OK" but didn't like it one bit better than other, more traditional multi-form Access applications they used. It seemed like a great idea, but didn't turn out as well as I had hoped it would.
I find the one in A97 to be very handy. Several of our forms have 10 or so tabs on them. And the system is somewhat less than half done. If'n I ever make it down to Texas, and as it happens there's a good chance of that in the next year or two, no wait, maybe I can arrange a stopover in Houston in January, we'll buy each other large amounts of beer and swap stories.
Newsletters may contain advertising. You can unsubscribe at any time. Hi Everybody, I have a query which uses 4 tables and each table has a one to many relationship with another table. I want to update some of the fields in the dynaset.
But I cant do that. Is there any way to work around this problem. Can I use a macro or anything else…. Sometimes changing the query type to Dynaset Inconsistent Updates will allow the updates to happen….
Is there anyhting else that I can do? I agree. The test is whetehr one can go directly to the query datasheet result and edit that. If not one must follow your suggestion. It is not a failing of Access but having not enough understanding of the menaing of the query itself, gained from experience and study, to realize that usually the query is too remote from the soirce tables to make such editing meaningful.
Would ti be possible from such an abstraction of records to walk back manually to records and edit them and be certain one is editing the correct or only ones?
0コメント