Crashing my IDE
If I open the report designer and then close it and try to run my
application to test the changes to the report 50% of the time I will get a
list out of bounds error and my IDE will crash. If I never open the report
designer I can run my application over and over with no issues. Only
happens if I open the report designer. I am using D2007 and RB 11.04. Any
one else experiencing this?
thanks in advance,
Rodger Van Kirk
application to test the changes to the report 50% of the time I will get a
list out of bounds error and my IDE will crash. If I never open the report
designer I can run my application over and over with no issues. Only
happens if I open the report designer. I am using D2007 and RB 11.04. Any
one else experiencing this?
thanks in advance,
Rodger Van Kirk
This discussion has been closed.
Comments
I recommend updating to RB 11.05 and then re-test.
Prior to installing RB 11.05, follow these steps.
http://www.digital-metaphors.com/rbWiki/General/Installation/Cleaning_Up_a_Corrupt_Install
If you did not receive notifcation about RB 11.05, please send your serial
number and registration details to info@digital-metaphors.com. Also, please
configure your spam/junk filters to allow email from our domain.
--
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
I have done this and it still happens. I'm going to try it again with Build
3 that I'm downloading now. It appears my List index out of bounds always
has (164) at the end. Also it appears I have figured out one way to always
make it happen.
I open a Project containing a Report.
Right-click on the report and go into the designer.
Switch to a sub-report tab.
Switch back to the main tab.
Close the report designer.
Click on the run button in the toolbar.
Compiles.
Starts to run and error comes up.
Not sure if it would help or not but I have a number of components and tools
installed in my development environment. I could try to compile a list of
them if it would help.
Thanks,
Rodger Van Kirk