I have migrating Edb from 2.11 to 2.19B2. I use C/S mode.
Some complex SQL join don't work in 2.19 version. I have the message "ElevateDB Error #9999 Access violation at address 00584C5C in module 'edbsrvr.exe'. Read of address 00000000"
After search, i have isolated the problem.
I have the error if i write :
SELECT TABLE1.CODE_PARUTION
, TABLE1.DATE_PARUTION
, TABLE2.NB_EXEMPLAIRE
, TABLE2.NB_SOUSCRIT
FROM TABLE1
LEFT OUTER JOIN TABLE2 ON
  (TABLE2.CODE_REVUE, TABLE2.DERNIER_NO) = (TABLE1.CODE_REVUE, TABLE1.CODE_PARUTION)
  AND TABLE2.TYPE_ABO IN (:TYPE_ABO1, :TYPE_ABO2, :TYPE_ABO3)
WHERE TABLE1.CODE_REVUE = :CODE_REVUE
AND TABLE1.NO_PARUTION >= :NO_PARUTION_DEB
AND TABLE1.NO_PARUTION <= :NO_PARUTION_FIN
But if i write this :
SELECT TABLE1.CODE_PARUTION
, TABLE1.DATE_PARUTION
, TABLE2.NB_EXEMPLAIRE
, TABLE2.NB_SOUSCRIT
FROM TABLE1
LEFT OUTER JOIN TABLE2 ON
  (TABLE2.CODE_REVUE, TABLE2.DERNIER_NO) = (TABLE1.CODE_REVUE, TABLE1.CODE_PARUTION)
WHERE TABLE1.CODE_REVUE = :CODE_REVUE
AND TABLE1.NO_PARUTION >= :NO_PARUTION_DEB
AND TABLE1.NO_PARUTION <= :NO_PARUTION_FIN
AND TABLE2.TYPE_ABO IN (:TYPE_ABO1, :TYPE_ABO2, :TYPE_ABO3)
There is no error.
The problem seem coming with the optimisation index on join (CODE_REVUE, DERNIER_NO)

How soluce this problem without rewrite all SQL ?

Eric,

<< I have migrating Edb from 2.11 to 2.19B2. I use C/S mode.
Some complex SQL join don't work in 2.19 version. I have the message
"ElevateDB Error #9999 Access violation at address 00584C5C in module
'edbsrvr.exe'. Read of address 00000000" >>

Please send me the database catalog and table files for the query that is
failing, and I'll investigate further.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com

I continue my investigation. I have multiple database with the same structure on multiple server.
All databases have the error when i change only the edb server version.
There is no error when the database is empty.
It's seem that if i change the order of create secondary indexes, prepare produce this error or not (i'm not sure)
I try to simplify the problem for send to you a demo.
I have attached the real SQL code.

Eric,

<< It's seem that if i change the order of create secondary indexes, prepare
produce this error or not (i'm not sure) I try to simplify the problem for
send to you a demo. I have attached the real SQL code.  >>

If you can just send me a copy of a database on which it occurs, I can take
it from there.  I don't even need all of the table files, just the table
files for the tables included in the SQL that is failing.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com

This is the tables samples
Thanks

Eric,

<< This is the tables samples >>

Thanks.  However, in the future please just email them to me, or post them in the binaries newsgroup.
------------

Tim Young
Elevate Software
www.elevatesoft.com

Eric,

Actually, I'm going to need your database catalog also (edbdatabase.edbcat).

I tried using the table files with a catalog created using your DDL SQL table definitions, but they don't match the structure used with the table files for some reason (columns or indexes are different).

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com