Tim,

When executing following DDL statement against CDCollector database in
EDBManager
I get A/V.

CREATE TABLE TblGenerator2(
ID INTEGER GENERATED ALWAYS AS IDENTITY (START WITH 0, INCREMENT BY 1),
ID1 INTEGER GENERATED ALWAYS AS IDENTITY (START WITH 0),
ID2 INTEGER GENERATED ALWAYS AS IDENTITY,
Name VARCHAR(30)
)

Access violation at address 0055C734 in module 'edbmgr.exe'.
Read of address 00000000

Regards,
Michael

P.S. It would be nice, if the errors were also logged as text (or we could
copy to clipboard
from that label), so it is easy to copy\paste them into messages.

Michael,

<< When executing following DDL statement against CDCollector database in
EDBManager
I get A/V. >>

This will be fixed in build 2.  The workaround is to always specify the seed
and increment values.

<< P.S. It would be nice, if the errors were also logged as text (or we
could copy to clipboard from that label), so it is easy to copy\paste them
into messages. >>

In the EDB Manager, click on the current session in the treeview and then
click on View Logged Events.  You can copy the error message from the last
logged error event.

--
Tim Young
Elevate Software
www.elevatesoft.com

> << P.S. It would be nice, if the errors were also logged as text (or we
> could copy to clipboard from that label), so it is easy to copy\paste them
> into messages. >>
> In the EDB Manager, click on the current session in the treeview and then
> click on View Logged Events.  You can copy the error message from the last
> logged error event.
I tried that, however, it doesn't seem to log SQL errors. Could you check it?


Regards,
Michael

Michael,

<< I tried that, however, it doesn't seem to log SQL errors. Could you check
it? >>

Make sure that all event types are being logged in the EDB Manager under
Edit Options/Logging.  For some reason I think these options are defaulting
to un-checked (or did during the beta), which isn't correct.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,


> Make sure that all event types are being logged in the EDB Manager under
> Edit Options/Logging.  For some reason I think these options are defaulting
> to un-checked (or did during the beta), which isn't correct.
Thanks, I found the option and checked them all. It still only logs
Information events and no SQL errors.


Regards,
Michael

Michael,

<< Thanks, I found the option and checked them all. It still only logs
Information events and no SQL errors.  >>

I forgot to mention that EDB doesn't log SQL/filter compilation errors, row
lock errors, or row lock change detection errors because they are very
common.

--
Tim Young
Elevate Software
www.elevatesoft.com