This is probably a long shot, but I thought I would ask anyway..
I have an application I wrote back in the 90's in Omnis 7.3.5 that is still running (kind of like the Energizer Bunny..just keeps on going!) Its had no maintenance for years...
The application accesses a Sybase database which is hosted on an elderly Unix box that needs to go to the Great Recycler in the Sky..and the client would like to get rid of not only the server but Sybase as well and convert over to a SQLServer database.
The SQLServer database has been built - its SQL Server 2005 sp3..I set up an ODBC connection to it using the built in SQLSERVER driver. I can connect to it using the SQLServer Manager..so the logon has the right permissions to see the data.
I changed the Omnis library to use O7ODBC DAM instead of the SYBASE DAM..In the built in database browser in Omnis, I can see the list of tables..but any queries result in a hard failure of the application - throws up a 'Sorry I need to quit' message and a dump. I did a trace in the ODBC manager and can see it connecting to the SQLServer, issuing the query and getting a SQL Success message..
If I step thru the library using the debugger, the command that causes the same hard failure is a Fetch command.
Any ideas on why Omnis is going splat?