Re: Alpha 9 Platinum Edition keeps freezing
Mike
It was with 3210, which I don't think saw release to the general public (did'nt check in the release board-3210 was a beta though) that a 'major rewrite of the entire browse logic' was implemented. Came out with 3212 After that I have had more than a few problems. Have a app that on a tabbed object (each tab having otm linked tables) used to change tabs in a blink. Took 31 seconds with 3210. took 3-4 seconds to change rows on a browse using the up/down arrow keys. (This was on a new machine-on a older pentium it was completely unusable.)
I sent in a report and the entire app right after the release of 3212.
It has improved quite a bit by 3222. Performance that is. For me anyway.
(3210 did clear up, which are still clear, issues that made, in certain situations the browse absolutly unusable) I have a app that a button click opens a db and presents a form. (the same form with the slow, browse intensive tabbs) that locks up now unless I access a different db first. (using 3222)
I do what a previous post said and roll back to whatever worked until the next patch and then try that. If it does not work I send in a bug report. The issues do get resolved. Sometimes by the next patch, sometimes several later. Right now when I have to work with the section of the app that is so browse intensive I roll back to 3208. I suspect the performance/lockup issues were/are due to the browse - though you may be right about the a_case thing. Though I never had a problem with it.
Mike
It was with 3210, which I don't think saw release to the general public (did'nt check in the release board-3210 was a beta though) that a 'major rewrite of the entire browse logic' was implemented. Came out with 3212 After that I have had more than a few problems. Have a app that on a tabbed object (each tab having otm linked tables) used to change tabs in a blink. Took 31 seconds with 3210. took 3-4 seconds to change rows on a browse using the up/down arrow keys. (This was on a new machine-on a older pentium it was completely unusable.)
I sent in a report and the entire app right after the release of 3212.
It has improved quite a bit by 3222. Performance that is. For me anyway.
(3210 did clear up, which are still clear, issues that made, in certain situations the browse absolutly unusable) I have a app that a button click opens a db and presents a form. (the same form with the slow, browse intensive tabbs) that locks up now unless I access a different db first. (using 3222)
I do what a previous post said and roll back to whatever worked until the next patch and then try that. If it does not work I send in a bug report. The issues do get resolved. Sometimes by the next patch, sometimes several later. Right now when I have to work with the section of the app that is so browse intensive I roll back to 3208. I suspect the performance/lockup issues were/are due to the browse - though you may be right about the a_case thing. Though I never had a problem with it.
Comment