Window crashes with the addition of a new prompt. (AREV Specific) [Revelation On-Line Wiki]

Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 13 APR 2000 11:15:27AM Rod Morris wrote:

AREV Specific

I have a window that has been working well for over a year. When I added a new prompt everything still was fine. But, when I used the prompt order table (Shift F7) to re-order the new prompt the window crashes after entry of the first prompt after the key. The error message in the debugger is: "WINDOW Line 1 Variable has not been assigned a value". Removing the new prompt does not solve the problem. The new prompt is simple, no pre or post prompt links.

AREV 2.03 running on Windows 98

Thanks in advance.

At 14 APR 2000 03:27AM Curt Putnam wrote:

Since you are not crashing to DOS, I suspect that all prompts are not protected. That being the case, the best thing to do is to start with a backup of the window before the modes were made, and start over.

At 14 APR 2000 09:02AM Rod Morris wrote:

I have tried doing the same thing from a backup copy of the window but I get the same result consistantly. As long as I don't re-order the new prompt it is fine. However, once that is done leaving the first prompt after the key (which is filled automatically) the window goes down.

At 14 APR 2000 10:24AM Michael Slack wrote:

Here is a shot in the dark. Does any of your window processes work with particular prompt numbers?

What I'm think is most likely is that one of the prompts in the immediate area of your new prompt expects the next prompt to be a certain one. When it isn't there as expaected is gets all confused. I know that we have some window processes that use the prompt number to access other prompts. If we were to insert a new prompt, then we would have to go in and change all of the references to any of the following prompts (thier prompt number haveing been moved down one). So if a piece of code referenced prompt number 14 and a new prompt had bee inserted somewhere before that, we would have to go thru and change 14 to 15.

Michael Slack

At 17 APR 2000 04:33PM Dale Walker wrote:

As near as I can tell, the following is what is happening:

Up to the time that you added the prompt everything was ok.

When you added a prompt, it was ok until you resequenced the prompt order.

The error message seems to be typical of a symbolic field. Is this true?

Is there a final prompt for the cursor to "land"?

Dale

View this thread on the forum...