Discussion of open issues, suggestions and bugs regarding UniDAC (Universal Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
-
FredS
- Posts: 272
- Joined: Mon 10 Nov 2014 17:52
Post
by FredS » Wed 04 Apr 2018 17:49
Code: Select all
EDatabaseError: Cannot perform this operation on a closed dataset.
Call stack:
Code: Select all
5116b0bd dbrtl240.bpl Data.DB 3268 +7 DatabaseError
5117faed dbrtl240.bpl Data.DB 12487 +1 TDataSet.CheckActive
51184204 dbrtl240.bpl Data.DB 14895 +1 TDataSet.Refresh.@label
511836b5 dbrtl240.bpl Data.DB 14439 +1 TDataSet.BeginInsertAppend
511837a1 dbrtl240.bpl Data.DB 14468 +1 TDataSet.AddRecord
004b5e82 PA.exe DataMod 1704 +3 TDataDM.LookupServersAddAllStr
5118451d dbrtl240.bpl Data.DB 15024 +1 TDataSet.DoAfterRefresh
511831df dbrtl240.bpl Data.DB 14287 +8 TDataSet.Refresh
These Lookup tables are opened in a thread:
Code: Select all
procedure TDataDM.LookupServersAddAllStr(DataSet: TDataSet);
begin
ProcessHintMsg('Lookup Table ''Servers'' is active..');
Assert(TCustomUniDataset(DataSet).LocalUpdate, 'With LocalUpdate active, Data Changes are cached locally in memory');
DataSet.AppendRecord([AllStr, '%']);
DecrementLookupsCountinAsyncMode();
end;
Reverted to '7.1.4 (29-Sep-2017)' and all is well..
-
ViktorV
- Devart Team
- Posts: 3168
- Joined: Wed 30 Jul 2014 07:16
Post
by ViktorV » Thu 05 Apr 2018 06:21
We have already fixed the issue. This fix will be included in the next build of UniDAC.
We can send you a UniDAC night build including the fix. Please provide your license number and IDE version to viktorv*devart*com and we will send you a night build.
-
FredS
- Posts: 272
- Joined: Mon 10 Nov 2014 17:52
Post
by FredS » Thu 05 Apr 2018 16:38
Thank you Viktor but I'm going to skip that.
Let me explain why you desperately need to change your patching.
When you send out a release we expect a certain amount of testing has gone into that, although judging from my reports since September that's questionable..
After I spend time updating and installing within a minute a bug appears and is reported. Then our only option is to take an overnight build, essentially untested code that may be in Beta state?
The right thing to do is to generate 7.2.6.1 from the original tested code, so that at the very least only bugs are fixed and no new features are added.
-
ViktorV
- Devart Team
- Posts: 3168
- Joined: Wed 30 Jul 2014 07:16
Post
by ViktorV » Fri 06 Apr 2018 06:43
Thank you for the interest in our products.
UniDAC build with hot fix is planned for next week.
-
kneighbour
- Posts: 77
- Joined: Wed 08 Oct 2008 04:55
Post
by kneighbour » Mon 09 Apr 2018 06:26
sigh...I have spent DAYS on this problem after the latest update. Should have looked here first, I guess. And I agree - "wait until next week" is not a good answer. All of my projects are now dead in the water. I cannot send anything to any of our customers until this (and the other problem) is fixed.
I have looked at rolling back, but I do not have a full backup of every version - and I also use IBDac and you have to have matching versions. It is not a simple thing to roll back as I then have to integrate with FastReports, etc.
What a mess....
-
ViktorV
- Devart Team
- Posts: 3168
- Joined: Wed 30 Jul 2014 07:16
Post
by ViktorV » Wed 11 Apr 2018 14:26
The new UniDAC 7.2.7 with with hot fix for this issue is already available for download now.