error message upon entering certain transactions

[jsturgill]

I am a new user, and am liking the program. However, when entering some transactions, I get an error message

Line: 273
Message: error 5
Record out of range

upon which the program closes. When I restart PC, and verify, the transaction was seemingly entered correctly, and presents no problems in posting, etc.
I checked the online help as well as the manual, and can't find any reference to error messages of any kind.
Any help will be appreciated.

Thanks
Jim

[NeilZ]

I am a new user, and am liking the program. However, when entering some transactions, I get an error message

Line: 273
Message: error 5
Record out of range

upon which the program closes. When I restart PC, and verify, the transaction was seemingly entered correctly, and presents no problems in posting, etc.
I checked the online help as well as the manual, and can't find any reference to error messages of any kind.
Any help will be appreciated.

Thanks
Jim

First off, I would do a complete reindex of the files, you can find this function under the UTILITIES menu. Make sure everyone is out of the system if you have it networked for multiple users.

Then if this happens again, come on back and give as much info as you can:

version of Powerchurch:
version of WIndows:
What you were doing when the error occurred (IE: What module you were in, what screen were you on, and so on) For example: Contributions, Enter Oontributions screen, clicking the SAVE button.

[jsturgill]

Thanks! I'll follow your instructions, and then see if it happens again.
Jim

[jsturgill]

I think I accidentally figured out what was happening, i.e. error message. Upon entering the amount in the transaction line, I was hitting the down key, or else clicking in the next line down, to get the save button to light up, and each time, it would give me the error message and close the program. I tried clicking in the other window of the same line, and that would give me the save button without the error problem.
Thanks for the attention,
Jim

[tborgal]

Could you give us a little more information about what you were doing so that if others are having the same issue they will be able to resolve it. I tried to recreate the problem here and could not but I may be working in the wrong module. If you could respond with the information that Neil asked for it would be very helpful for all.

[NeilZ]

I agree ... while I'm glad you figured out the problem, I'm still puzzled at what you were doing at the time

[jsturgill]

In the accounting module, while entering transactions, upon making the last entry, the accounts were still "unbalanced", so I would hit the down key, or click in the next line down, which was blank. It was at this point I would get the error 5 message -- "out of range", and the program would close.
Once I began clicking in another box ON THE SAME LINE, the accounts would balance, and the save button would light up, and everything proceeded normally.
I hope this clarifies the situation enough to be understandable, even though it's in "newbie" language

Thanks again.
Jim

[jsturgill]

I forgot to answer Niel's questions in the previous post -- sorry...

version of Powerchurch:
version of WIndows:
What you were doing when the error occurred (IE: What module you were in, what screen were you on, and so on) For example: Contributions, Enter Oontributions screen, clicking the SAVE button.

My PowerChurch is 11.5
I'm using Windows 7
What I was doing, and in which module/screen, I think is in the previous post.
Jim

[tborgal]

Jim,

I tried with no success to recreate the problem you describe. What do you mean when you say you hit the down key, the down arrow or page down? Also what do you mean when you say the save button lights up? There is no change in any of the buttons on the form until I put my cursor over them and they all react the same way whether the transaction is in balance or not. What Maintenance Release are you on? Select Help> About Power Church Plus> System Information. Your program date should be 03/19/2012. If it is not you should update to the new release and try to recreate the problem.