Page 2 of 2
Posted: Tue 15 May 2007 20:56
by Ludek
Well, this could be perhaps possible. Do you have an idea, how this could be done automatically, without modifying the body of thousands
triggers manually? I'm only afraid, that I forget these 2 commands in that triggers, which will be programmed in future, when my brain gets full of other important things... I would really LOVE
such simple option "useFirstAffectedRows: boolean" so much... Is it really so complicated? It would make me (perhaps also many other SDAC users of today and tomorrow) very happy
Posted: Thu 17 May 2007 14:54
by Ludek
Posted: Thu 17 May 2007 15:50
by Ikar
We are investigating the problem right now. During a couple of days we will notify you about a solution by e-mail.
Posted: Mon 21 May 2007 06:24
by Ludek
I'm looking forward to it
Posted: Mon 11 Jun 2007 12:54
by jfpicard
Any solution ? We have the same problem here.
Thanks.
Posted: Mon 11 Jun 2007 14:17
by Ludek
Yeah, it should be solved in 4.0.0.8 using a option
And, as you can read in other topic, this version should be available in couple of days
Posted: Fri 10 Aug 2007 13:44
by chedom
I have 4.10.0.10 and the same problem. Is there a solution?
Posted: Fri 10 Aug 2007 15:35
by Ikar
Try to set global variable __UseUpdateOptimization to False.
Posted: Thu 27 Dec 2007 12:28
by tulu
Ikar wrote:Try to set global variable __UseUpdateOptimization to False.
How and where do we do that? __UseUpdateOptimization := false does not work when in project source.
I have this problem and now almost all app is unusable. Error reports are flowing. :cryl:
Posted: Thu 27 Dec 2007 13:23
by Antaeus
Most likely the problem you have encountered differs from the problem discussed in this topic. Please, read the description of TCustomDADataSet.Options.StrictUpdate in SDAC help.
If you find no appropriate solution, please, describe under what conditions does the problem occurs:
- architecture of your project;
- on what operation does the problem occur;
- SQL statement that is executing when the problem occurs;
- values of SQLUpdate, SQLRefresh properties;
- any other information that can be useful.
You can post this information in this thread, or send it to me by e-mail at sdac*crlab*com.
Posted: Thu 10 Jan 2008 16:30
by tulu
initialization
MSAccess.__UseUpdateOptimization := false;
works. Now updates/inserts do not return the error. Thank you.