Release of Zeos 8.0.0

[marsupilami]

The Zeos Team is proud to announce the availability of Zeos 8.0.0 as a stable release. This is the newest stable version of Zeos. It deprecates Zeos 7.2, and any previous version of Zeos. We urge all people still using older versions of Zeos to upgrade. If you have any problems with Zeos 8.0, please get in contact with us on the forums or on the bugtracker.

The most outstanding changes in Zeos 8.0 are

• Support for Delphi NextGen compilers to support Android, iOS and Mac OS X
• Two new bridge drivers for OleDB and ODBC
• A new driver that uses the Firebird interface based API for accessing Firebird versions 2.5 and above
• A special proxy server and an according driver that can be used to access any Zeos supported database using SOAP over HTTP(S) from (mobile) clients.
• Propper support for numeic and decimal fields by using TBCDField and TFMTBCDField
• Nested transactions using savepoints
• Two new components: TZTransaction and TZMemTable
• better overall performance and smaller memory footprint

Besides these improvements Zeos has seen a ton of other additions and improvements. For an overview of the changes in Zeos 8.0 see the release notes.

To download, the new version of Zeos please use this link.

[ChrisFri]

Hi, I'm using Delphi12 and wanted to use the ZeosDBO. When compiling the project group, there is an error: "Remove ZPropertyEditor, ZComponentReg.
The unit(s) ZPropertyEditor, ZComponentReg were found in the required package ZComponent." When I install the finished packgage, no components are visible there. What am I doing wrong? Best regards, Christian.

[jqmicrosistema]

I have an error using Zeos with Lazarus. I am getting the error
System Error :Code(193)
This is when I try to connect in design mode with property "Conected"

[marsupilami]

Which version of Lazarus and FPC do you use? How is the configuration of you TZConnection object? Can you maybe share a sample application that generates the probelm?

[stevetreesh]

Platform Lazarus 3.4

Does 8.0 support LongText fields in MS Access 2016? Doing an EDIT with ZTable of LongText data throw exception on POST. After extensive testing it appears the LongText type field is limited to 510 chars on an INSERT/EDIT. The following exception is thrown:

Project Test raised exception class 'EZDatabaseError' with message:
value of param 0 exceeded
Stmt: UPDATE A_TEST SET TEST=?, CREATED_DATE=? WHERE ID=?

Column TEST is a LongText and the input value has 511 chars. The POST does not fail at 510 chars.

[marsupilami]

Hello,

we don't do specific tests on MS Access. What kind of column does Zeos generate for that field? TWiedeMemoField? TWideStringField?

Could you maybe post the sample app that you use to test this?

Best regards,

Jan

[stevetreesh]

From: Steve Treesh

Here's a test program I just ran with failure.
----------------------------------
Lazarus version 3.4 - 32 bit -- Also Tested on Delphi 7 - same failure
ZEOS 8
Windows 11
Microsoft Access 2019 - 32 bit
----------------------------------

If you don't have Access, I can send you a small DB file (accdb)

Test Code:

procedure RunTest;
var
r : integer;
l_Ok : boolean;
l_Id, l_Str : string;
l_TextLength : integer;
ZDB : TZConnection;
ZTab : TZTable;

function CharStr(p_Char: char; p_Len: integer): string;
begin
result := '';
while Length(result) < p_Len do
result := result + p_Char;
end;

begin

{-- Test Table Structure and Data

CREATE TABLE A_TEST
( ID INTEGER,
SHORT_TEXT_1 TEXT,
LONG_TEXT_1 LONGTEXT
);
INSERT INTO A_TEST VALUES(1,'','');
--}

l_Ok := False;
l_Id := '1';

ZDB := TZConnection.Create(Nil);
ZTab := TZTable.Create(Nil);

try
ZTab.Connection := ZDB;
ZDB.Database := 'Provider=Microsoft.ACE.OLEDB.12.0;'
+'Data Source=C:\TEMP\TEST.accdb;' //<<-- my location
+'Persist Security Info=False';
ZDB.Protocol := 'OleDB';
ZDB.Connected := True;

with ZTab do
try
Close;
TableName := 'A_TEST';
Open;
if Locate('ID',l_Id,[]) then
begin
Edit;
FieldByName('SHORT_TEXT_1').AsString := CharStr('A',200);

l_TextLength := 511; // adjustable here
l_Str := CharStr('A',l_TextLength);

//-------------------------------------------------------
//-- None of the following work with text lengh > 510
//-------------------------------------------------------
FieldByName('LONG_TEXT_1').AsString := l_Str;
// FieldByName('LONG_TEXT_1').AsWideString := l_Str;
// FieldByName('LONG_TEXT_1').AsAnsiString := l_Str;
// FieldByName('LONG_TEXT_1').AsUnicodeString := l_Str;
// FieldByName('LONG_TEXT_1').AsUTF8String := l_Str;
// FieldByName('LONG_TEXT_1').AsVariant := l_Str;
// FieldByName('LONG_TEXT_1').NewValue := l_Str;
// FieldByName('LONG_TEXT_1').Value := l_Str;

try
Post;
Close;
l_Ok := True;
except
on E:Exception do
begin
l_Ok := False;
Close;
ShowMessage('Error: ' + E.Message);
end;
end;
end;
finally
Close;
end;
finally
if l_Ok then
ShowMessage('Success');
ZDB.Connected := False;
FreeAndNil(ZTab);
FreeAndNil(ZDB);
end;
end;

[pitterson]

Hi, I'm using Delphi12 and wanted to use the ZeosDBO. When compiling the project group, there is an error: "Remove ZPropertyEditor, ZComponentReg.
The unit(s) ZPropertyEditor, ZComponentReg were found in the required package ZComponent." When I install the finished packgage, no components are visible there. What am I doing wrong? Best regards, Christian.

Hello, Christian. Delphi12 gets to be having issues with ZeosDBO as a result of obsolete or outdated units. Make sure you have the correct version of ZeosDBO for Delphi12 and that all paths are properly configured. Reinstalling the package and checking for updates may help.

[pitterson]

Hi, I'm using Delphi12 and wanted to use the ZeosDBO. When compiling the project group, there is an error: "Remove ZPropertyEditor, ZComponentReg.
The unit(s) ZPropertyEditor, ZComponentReg were found in the required package ZComponent." When I install the finished packgage, no components are visible there. What am I doing wrong? Best regards, Christian.

Hello, Christian. Delphi12 gets to be having issues with ZeosDBO as a result of obsolete or outdated units. Make sure you have the correct version of ZeosDBO for Delphi12 and that all paths are properly configured. Reinstalling the package and checking for updates may help.