Omnis 6.1.x PITA

[Alain Stouder Omnis]

Not sure what it means for the future of Omnis but the cost & burden of being a small listed company will be solved.

---
Learn something new everyday!

> On 26 févr. 2016, at 18:58, Andrew Stolarz <stolarz at gmail.com> wrote:
> 
> Hi Mats,
> 
> 
> I feel your frustration.
> 
> 
> I have Omnis crashing on me often running 6.0x. Iv gotten to the point of
> saving everything each time I want to test a window so I don’t have to
> re-do code as you mention (Mine does not crash as frequent as yours and
> happens more so in the remote JS forms then the thick client). I don’t
> experience those other issue you mention, but I’m also not currently
> running 6.1.x
> 
> My thick client runtimes have essentially been "bulletproof" so to speak.
> 
> Most of my frustration currently is with the JS client.  Iv spent more time
> in the last two months trying to resolve the Omnis web server crashing at
> random times then actually writing code. While I have been working with TL
> on this matter for almost a month now, they can’t seem to find a
> fix/solution to the problem. As much as I like to use Omnis, at the end of
> the day if my customers are cancelling due to frustration, how much longer
> can I continue with the JS client?
> 
> TL support team has been very helpful in trying to resolve this for me, but
> I believe it’s the reduced R&D / engineering time causing this spiral
> effect to a lot of unresolved/ underdeveloped issues as you listed out. I’m
> not sure if you are aware, TL is looking to sell off the Omnis business
> unit and dissolve TL.  I trust that TL will find an amazing new home for
> Omnis.
> 
> 
> http://www.tigerlogic.com/tigerlogic/company/press/2016_02_18.jsp
> 
> Talking with TL/Omnis, They are committed on delivering studio 8 as
> scheduled.
> 
> 
> 
> 
> Andrew
> 
> 
> 
>> On 26 February 2016 at 08:56, Phil (OmnisList) <phil at pgpotter.co.uk> wrote:
>> 
>> Hey Mats,
>> I don't use 6.1 yet, but your experience doesn't sound good.
>> 
>> Do you have any idea what they meant by 'bad coding'?
>> Are they blaming the corruption to the same cause?
>> 
>> ODB, I haven't used ODB for ages, and  would only do SQL now, so I have no
>> comment on this.
>> 
>> What SQL cuts you off?
>> People have mentioned about a ping like method to keep a connection alive,
>> are you doing that?
>> and its not clear why a reconnect would take a long time?
>> does the normal first connection also take a long time?
>> 
>> ODB messages.txt
>> what ODBLogLevel are you using? (found in the config.xml file)
>> 
>> Omnis.cfg
>> I've often had an issue with this file, but using a serial.txt keeps the
>> serial number, and most everything else is not important.
>> Is it the lack of the serial number that is the problem?
>> then the serial.txt will resolve that.
>> 
>> regards
>> Phil Potter
>> Based in Chester in the UK.
>> 
>> 
>> 
>>> On 26/02/2016 12:47, ADJob wrote:
>>> 
>>> 1. Omnis 6.1.x crasches frequently
>>> ——————————————————————————————————————————————
>>> 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”.
>>> 
>>> 2. Omnis corrupts code randomly causing errors and time loss
>>> ——————————————————————————————————————————————
>>> Verified once and minor crash corrected by TL.
>>> 
>>> 3. Spinning wheel ODB.
>>> ——————————————————————————————————————————————
>>> 
>>> 4. Spinning wheel SQL.
>>> ——————————————————————————————————————————————
>>> Inactivity causes the session to stop. Reconnecting takes looong time.
>>> 
>>> 5. ODB messages.txt goes nuts.
>>> ——————————————————————————————————————————————
>>> The messages.txt is sometimes filled with gigabytes of errors until the
>>> server stops working.
>>> 
>>> 6. Licens issue #1: Cannot read omnis.cfg
>>> ——————————————————————————————————————————————
>>> Cannot start application because of omnis.cfg corruption.
>>> 
>>> 7. Licens issue #2: ODB connection disruption
>>> ——————————————————————————————————————————————
>>> When the connection to ODB are disrupted, the license are not cleared.
>>> 
>>> Next generation of my software built with Omnis? The clue should be
>>> obvious.
>>> 
>>> Struggling with Omnis since 1985…
>>> 
>>> /Mats
>>> 
>>> _____________________________________________________________
>> Manage your list subscriptions at http://lists.omnis-dev.com
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com
>