Powerplay 6.61 and Windows 2000 1

[ukflix]

When a fairly complex report is created and saved with Powerplay 6.61. When the user tries to open it again it crashes and we get a memory could not be read error also the report is coorupted and cannot be opened by any other person. This is not the most complex report in the world and if it is run using the same version of powerplay but on windows 98 it works OK. We have tried this on several different computers and run it as as administrator all with the same results. Has anybody seen anything like this before or does anyone no how to get around it???

 

[Waspy]

Make sure your on RBF3 at least - 6.61 700 (Help/About) as this is the most stable version. Also, set your undo steps(properties) to zero, close the client, re-open it and then create and save the report. Only things I can think of, sorry =)

 

[ukflix]

Why do you say set the undo steps to 0? Do you suffer from the same bug too where resources are eaten away?

 

[Waspy]

There was a bug in the memory management in the UNDO function. This caused a memory leak which could cause crashes. Just a suggestion that may work =)

 

[ukflix]

Waspy, Do you have any more info about the Undo Bug please? ie. How do you know it exists? How do you prove the bug? Is it still present in version 7 (I think it is)? We still have some users on version 6.5 as this version works well and cannot upgrade them due to the way they work with Powerplay. Appreciate your input. Thanks.

 

[Waspy]

Sorry, no more information. I know it exists as I have seen it myself, and also I have advised people to reduce it to zero in a number of cases and it has resolved memory problems. To test if it is, simply do as I said - reduce it to zero, and re-test the problem reports. It is definately not present in 7 - if the issue still occurs in 7 it is something else. Hope this helps