Zeoslib Portal

My question is in the moment i start a new record in ( clients ), ( clients_phones ) should start a new record too or i am wrong ? Depends on the constraints you set in your create table statements. Could you post the create statements for detailed information? If there is no constraint, which I as...

I think you need the fields of at least the master-dataset in the corresponding field editor (right click on the dataset (query or table) and chose field editor,
right click in the field editor an chose add all fields)
should work

btw. Moin Moin von der Ostsee!

Don't know the reason but I assume, the user property is used as some kind of default value for connecting silently and is not written back by manual login, cause this could cause some inconsistency: in case you close the connection and reconnect user and password properties could be used to connect...

Never heard of that (referencing to another module i.e. unit).

But go ahead, put it in the uses clause of the unit where its needed an you'll see it won't do any harm. And your program (?) will only grow a tiny little bit bigger, in case your afraid of the size of your exe.

Couldn't you use TZQuery instead of TZTable? You could build an SQL-statement like: SELECT ...., 'limit' [as] new_limit FROM .... WHERE ... So your field name would be new_limit instead of 'limit'. If you have to use [as] (without the [ ]) depends on the SQL dialekt. This idea is really a workaround...

ZQuery1->Connection = g_DbConn[g_DbsCap].pConn;
ZQuery1->SQL->Text = "SELECT * FROM cnpProduct";
ZQuery2->RequestLive = true;
ZQuery1->Active = true;

Is it just a copy-paste-error that ZQuery2.RequestLive is set to true instead of ZQuery1.RequestLive?

Could you be a little more precise?

Are you running the same version of MySQL on both machines? Which version(s)?

How do you insert/update records? ZQuery.Edit, Zquery.Post or manual with sql statemants (Update x set y=z where a) ?

[equote] What is the equivalent in Zeos 6.6 for zeos 5.4..........................zeos 6.6 TZMysqlDatabase............TZConnection ??? TTMysqlQuery.................TZQuery ? TZMysqlTransact...............???? TDataSource....................???? [/equote] I started Zeos with 5.5 AFAIR, so I'm quite s...

I needed to remove all Zeos dcp and bpl files from <DELPHIPATH>\Projects\bpl to get the new (6.6) installation working. Did you try that?

I tried using stuff like: ZQuery1.SQL.Text := 'SELECT COUNT(*) FROM `users` WHERE ostatus = "Offline";'; And the using .RecordCount but I always get a return value of 1 from RecordCount, without the WHERE it returns the correct number of rows. Sounds a bit strange to me too, since ZQuery1...

Hi!

I experienced a similar problem some months ago. I don't know anymore exactly under which circumstances they appeared, but I solved it using the keyfield of the table instead of *. Maybe that helps.

Btw: you do not try to get the result with ZQuery1.recordcount, don't you?

I tried the embedded example from 6.6.0 with libmysql41d.dll and libmysql5d.dll. I always get an Access Violation on address 0000000 when trying to open the ClientDataset. Connection to the database works without an error. Everything else with the new 6.6.0 works fine. Any ideas? I forgot: I'm using...

That's true. The update is a must-have, and as fduenas said, 6.6 is quite stable right now. You may expend some time converting request live to read only property, but all other changes are, as far I know, "backward" compatible, so it's compile and run Yes, it is a must have, but it was n...

Hm, hab mir Dein Programm mal runtergeladen und auch ein neues mit 6.1.5 gebaut. Das scheint irgendwas an Deiner Access-Datenbank zu sein. Bist Du sicher, daß mit der mdb alles OK ist? Habe kein Access auf dem PC und daher versucht mit MDBPLus an die MDB zu kommen: keine Tabelle zu sehen. Ist das Ac...

I'm still using 3.23.xx (wth 6.1.5), but I am looking forward to the 6.5.1 becoming at least beta, so I can switch to MySQL 5 or PostgreSQL 8. If the beta and final will arrive maybe a little earlier without the 3.23.xx support it's more than fine with me to drop that feature. By the way: very speci...