Community
Showing results for 
Search instead for 
Do you mean 
Reply

ERROR MESSAGE: "Index - 1 does not have a value."

New Member
Posts: 1
Country: USA

ERROR MESSAGE: "Index - 1 does not have a value."

[ Edited ]

Hi Community:

 

I am using ACT! Pro 2011 Version 13.1.111.0, Hotfix 5, and I keep getting the following error message:  Index - 1 does not have a value.

 

Any suggestions on how to correct this problem would be appreciated.

 

Thank you,

 

Kevan

Platinum Super Contributor
Posts: 5,275
Country: USA

Re: ERROR MESSAGE: "Index - 1 does not have a value."

Hello Kevan,

Welcome to Sage ACT! Online Community!

 

Be sure to run maintenance on your database; here is an article with instructions: KB Article 26038

 

If this does not resolve your issue, please provide additional information:

- Operating System?

- What steps taken when error presented?

- Shared database?

- If shared, do other users also get the error?

Greg Martin
Sage
Copper Contributor
Posts: 37
Country: USA

Re: ERROR MESSAGE: "Index - 1 does not have a value."

I am also getting this error on different machines- Win7(server), XP Pro, other Win7 workstations
I have tried all maintenance and rebuilds
Yes it is a shared database
thoughts?
Platinum Super Contributor
Posts: 5,275
Country: USA

Re: ERROR MESSAGE: "Index - 1 does not have a value."

Please provide the steps/function that present the error.

 

Does it happen on each workstation, or just some of them? 

 

If it only occurs on some workstations, try signing into ACT! on a workstation that doesn't have the error with a username from a workstation that does receive the error.  This will test to see if the error follows the username.

Greg Martin
Sage
Copper Elite Contributor
Posts: 175
Country: USA

Re: ERROR MESSAGE: "Index - 1 does not have a value."

Did you find a resolution?  I'm getting the same error on both the server and client and after running maintenance. The error occurred when I did this:  1) On the server, In define fields, I changed the ID/Status field to allow for it to be empty, 2) Then I ran the maintenance. The error popped up after I completed the maintenance. After closing the error window, behind it was the window for the maintenance saying it had completed successfully.  However, I get the exact same error on the client station and it had yet to sync after that change was made on the server. So, it must to be a cause of the field change.