Omnis 6.1.x PITA

[ADJob]

Hi $all,

What do you do when the normal channel (support, management) not are giving any result? And your situation is beginning to be desperate? 

I am losing at least a MONTH every year trying to recreate all non saved code caused by crashes and/or corrupted code.

The purpose of this letter is to use this channel to express my problem. Hopefully finding some solutions and perhaps giving some valuable information about 6.1.x. 

Will this lead to the knowledge I am not alone, it should be both negative and positive.

My problem started with 6.1.x. None or just minor problems with 5.x.  Here is some of the problem: 


1. Omnis 6.1.x crasches frequently
——————————————————————————————————————————————
The crashes occur when I am in the developer mode using 6.1.x. The same does not happen in 5.x. 

Problem: Code is not saved and I have to manually find and replace all code once again. Frustrating and time consuming. At least 3 crashes a day. Loosing 10 minutes every crash being recreating non saved code. 

Action taken: Reported and send library to TL for investigation. Verified a couple of times by TL and corrected. They practically blame me for bad coding. ”the main reasons for the crashes are lying in your code”. Without telling me why. TL does not admit that the problem exist.

Status: No fix either done or announced.


2. Omnis corrupts code randomly causing errors and time loss
——————————————————————————————————————————————
Several times a week old code stops working. Looking into it, the original method is replaced by another random method.

Problem: Finding the coruppted code and replace with backup is time consuming and frustrating.

Action taken: Reported and send library to TL for investigation. Verified once and minor crash corrected by TL. 

Status: No fix either done or announced. TL does not admit that the problem exist.


3. Spinning wheel ODB.
——————————————————————————————————————————————
Sleep, Wifi, moving laptops etc. Working with cable does not solve all problems. The license are not logged out correctly when forced quit and Omnis stops working for my customers. I have loosed several customers that claims that my application is not reliable.

Note that 5.x does not have any problems with Yosemite and Wifi. So I think to blame Apple is not constructive.

Problem: Causing license lockout and customer frustration

Action taken: Reported. Verified by many. 

Status: No fix either done or announced.


4. Spinning wheel SQL.
——————————————————————————————————————————————
Inactivity causes the session to stop. Reconnecting takes looong time.

Problem: Causing customer frustration.

Action taken: Reported. Verified once. 

Status: No fix or suggestions either done or announced.



5. ODB messages.txt goes nuts.
——————————————————————————————————————————————
The messages.txt is sometimes filled with gigabytes of errors until the server stops working. 

Problem: Customers being annoyed.

Action: Reported and confirmed.

Status: No fix either done or announced.



6. Licens issue #1: Cannot read omnis.cfg
——————————————————————————————————————————————
Cannot start application because of omnis.cfg corruption.

Problem: Customers are annoyed.

Action: Reported and confirmed.

Status: Fix are suggested (not announced) to Omnis 8 (not confirmed).



7. Licens issue #2: ODB connection disruption
——————————————————————————————————————————————
When the connection to ODB are disrupted, the license are not cleared.

Problem: Customers are annoyed because they are prohibited by the ”shadow license”.

Action: Reported

Status: No fix either done or announced.



Next generation of my software built with Omnis? The clue should be obvious.

Struggling with Omnis since 1985…

/Mats