Visual LANSA Forum

Hi Art,

I was surprised to hear you say you had a patch for 142030, I have no idea how you got away with applying a patch for 142060 onto 142030... that sounds like a bit of a miracle

Hi LANSAfolks,

if you're concerned about crashes you could at least get up to EPC142060 and/or talk to support.... not much anybody can do to help you on this forum

Cheers,
Danny

A hotfix for the IDE doesn't scare me much. The install has a backout feature but I've never had to use it.

For the popup crash, is this your problem?

viewtopic.php?f=3&t=2227

In my experience, the only way of making headway with random IDE crashes is to zip up the (enormous) dump file and get it sent to the devs. Often, they can pinpoint the issue and provide a fix. So, that would be my suggestion for your random crashes (but if you don't like to apply hotfixes, you might have to live with them).

I click save and check in ALOT. Today save was 20 seconds for a relatively small RP, and the check in window took forever to come up.

I closed everything on my pc except the IDE and even task manager Closed all the google chrome stuff, and it was still the same.

I keep saying I’m going to test this, but do I have to save before I click check in on the open component?

Here is a short video that shows the IDE problem I have. You can sort of hear me mashing on the keys so you can tell that I'm typing.

https://youtu.be/3P2SutUjDXI

Hi Art,

Looks Auto Complete related.... just to confirm, does it go away if you turn Auto Complete off?

Danny

Next time it happens I will turn it off and keep testing. Thanks

pkoopmanpk wrote: Wed Nov 06, 2019 8:37 pm The suggestion to use the SQL Native client version 11 is a good start.

The time for the source that took nearly 2 minutes to close with ODBC Driver 11 for SQL server, went down to 40 seconds.
On a second PC with ODBC driver 13, it also went down from 1 minute to 40 seconds.

This weekend we installed EPC142067. The time to close our 'monster' source went from 40 second to 60 seconds.

Hi,

As mentioned earlier in this thread, there is a patch available.

I would talk to support.

Cheers,
Danny