Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index
Hello
When i expert a report in excel it gives me this errror: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index
It is so strange to me, the report itself is fine, it works with my old database, but recently i upgraded to a cloud solution and it gave the above error. All other reports work but this.
Any suggestion?
When i expert a report in excel it gives me this errror: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index
It is so strange to me, the report itself is fine, it works with my old database, but recently i upgraded to a cloud solution and it gave the above error. All other reports work but this.
Any suggestion?
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
All that error message is stating is that the collection you are accessing with the index is less then 0 which is not valid because a list only has positive index starting at 0 or the index you are using is greater then the number of elements in the collection which is invalid because the last index is one less then the total number of elements in the collection because collections are zero based index.
Can you post the code where this is happening please.
Can you post the code where this is happening please.
I understand,
to me what makes it more weird is the the same code works fine when connected to my old database, the error does not show, once i connect it to the new database which it should be identical, the error shows up. It sounds to me that something within the database is bothering it. I have a lots of coding on this as it involves a whole report but I will and see if i can find anything within the database. Thanks
to me what makes it more weird is the the same code works fine when connected to my old database, the error does not show, once i connect it to the new database which it should be identical, the error shows up. It sounds to me that something within the database is bothering it. I have a lots of coding on this as it involves a whole report but I will and see if i can find anything within the database. Thanks
Premium Content
You need an Expert Office subscription to comment.Start Free Trial