Zeoslib Portal

Not sure if this leads to a solution, but confusing enough, on a 64 bit system the System32 is for 64 bit dll's and wow64 is for 32bit dll's. So if you have installed a 32bit version of mysql LibMySql.dll should be placed in wow64, otherwise in system32. Read more on http://webmechs.com/webpress/200...

Zeos7 is compatible and runs on firebird 2.5 utf8, but i would be carefull as zeos 7 can also completely crash your production environment as i have found out (Row buffer width exceeded. Try using fewer or longer columns)

TBytes is not supported for older versions but is very easy to introduce. Just a ifdef and typedef TBytes = array of Byte will do the job. I have currently no idea about the impact of this.

Unfortunately i'm afraid i cannot make the time at this moment so for now we have fallback on Anydac.

After finally switching my database to UTF8/Dialect3 i'm getting the SRowBufferWidthExceeded error (obviously since each varchar(200) is now occupying in reality 800 bytes) This condition seems to have todo with with the TByteArray = array [0..32767] of byte. Why is Zeos using such a limited buffer?...

Marius2 , Are you joking with us? Don't you remember this old post : http://zeos.firmos.at/viewtopic.php?t=2142 Mark LOL i wish Mark That was a while ago and since then came zeos database, then unicode and zeos was far from prepared for that. So to get our products working with unicode we switched ...

Sorry, we are using the latest 7.0 beta via svn and are using 2010 (and soon delphi XE i hope)

Yes its easy, but it wil not work AFAIK.

Im trying to compile on delphi XE but im getting 3 error like this one.... [DCC Error] ZSysUtils.pas(454): E2010 Incompatible types: 'PAnsiChar' and 'PWideChar' Check the zeos.inc and look for "{$IFDEF VER220}". If its not there a lot of ifdefs go wrong during compilation. Copying the del...

Editing a query result is useless.

Instead write an update sql.. update table set field=:value etc..

Labels are just labels. No, i definitely dont agree with that. Alpha is by definition a no-go for production releases, a beta is signaling its ready but could contain minor errors.. So are you implying the alpha status could change in a beta status? (would be good for Zeos components in general). O...

If you compare the two versions you'll see not much has changed (except for the needed unicode changes). I have been testing recently with firebird and that seems quite reliable, i haven't tested mssql yet and oracle is a total failure at this moment (it truncates string fields).

I just revived Zeos after 2 years, we need a component set which works with firebird, mssql and oracle (and problably some others as well in the future). Is anybody working on the oracle OCI layer and is there any news/improvements? I'm not afraid to look into this, but i'm totally new in the oracle...

Thanks Guido, I have hundreds (mayby even thousands) of hardcoded queries with double qoutes so this solution would cost us a lot of time to correct and test. Like you suggested i use query parameters these day's to avoid the quote clutter. Unidac and anydac dont complain so i expected something sim...

I'm a returning user wanting to replace unidac and anydac with good old zeos again (as unicode seems to be working now). My problem, i have a simple query: select * from table_name where field_name="field_value" On which i get the following error 'SQL Error: Dynamic SQL Error SQL error cod...

Fair ;) but new aint better, that "silly" old mainframe still works faster and better as most modern computers! Anywhay, if the parser goes bananas its an error as i clearly have setup a dialect 1 db, and i cant go back now because DBX was randomly returning errors in dbexpint.dll (stupid ...