When updating to 2.03B6, please avoid to mix < 2.03B6 servers with >= 2.03B6 clients. If you do it, when opening a store you get "Field ModifiedOn
not found" error due this field is new in this version and old server don't create it, but new client is looking for it.

I request for this field to Tim, please sorry for the inconveniences caused for this enhacement

Tiago,

<< When updating to 2.03B6, please avoid to mix < 2.03B6 servers with >=
2.03B6 clients. If you do it, when opening a store you get "Field ModifiedOn
not found" error due this field is new in this version and old server don't
create it, but new client is looking for it.

I request for this field to Tim, please sorry for the inconveniences caused
for this enhacement >>

A big clarification here - this only applies to applications that query this
table:

http://www.elevatesoft.com/manual?action=mantopic&id=edb2sql&category=3&topic=61

and actually try to read the ModifiedOn column.  IOW, it only applies to the
EDB Manager for 2.03 B6 and higher, as far as what we ship with the
ElevateDB.

--
Tim Young
Elevate Software
www.elevatesoft.com