Edgars Tjarve
Member
Hello!
Our company has a C# application, that attempts to connect to DSN of OneWorld Oda (JDEOWODA.dll V2.0.0.0) to get data from tables. We currently have Installed JDEdwards version 9.2.6.3 64Bit Client. Application is being developed on Win64 bit machine and for 64Bits. We are able to connect to driver just fine (when developer is not logged in, a JDE login form pops up) and upon entering credentials we get a successful connection. We are even able to use SQLTables (ODBC32.dll function method) to retrieve all tables that connection can see. But when we are trying to write any query and give it to our connection (any table, any request), we get a crash with error "System.AccessViolationException, Attempted to read or write protected memory" at ODBC functions SQLExecureDirectW and SQLPrepareW. It seems that we are doing everything correctly (setting ODBC version to "2" before connecting, setting handles correctly, tried various queries. And code used to work before (was changed to a different method but now we want to return to this method)), but couldn't find the cause of this issue. Does anyone have solved this issue or could help to put us on a right path?
P.S. We are even trying to test this with ODBCTest application (from Microsoft) but issue occurs there too
Our company has a C# application, that attempts to connect to DSN of OneWorld Oda (JDEOWODA.dll V2.0.0.0) to get data from tables. We currently have Installed JDEdwards version 9.2.6.3 64Bit Client. Application is being developed on Win64 bit machine and for 64Bits. We are able to connect to driver just fine (when developer is not logged in, a JDE login form pops up) and upon entering credentials we get a successful connection. We are even able to use SQLTables (ODBC32.dll function method) to retrieve all tables that connection can see. But when we are trying to write any query and give it to our connection (any table, any request), we get a crash with error "System.AccessViolationException, Attempted to read or write protected memory" at ODBC functions SQLExecureDirectW and SQLPrepareW. It seems that we are doing everything correctly (setting ODBC version to "2" before connecting, setting handles correctly, tried various queries. And code used to work before (was changed to a different method but now we want to return to this method)), but couldn't find the cause of this issue. Does anyone have solved this issue or could help to put us on a right path?
P.S. We are even trying to test this with ODBCTest application (from Microsoft) but issue occurs there too