Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

Newcomers DBPro Corner / Syntax error. Nesting error. Lines too long

Author
Message
047
18
Years of Service
User Offline
Joined: 4th Jun 2006
Location:
Posted: 2nd Jul 2006 00:48
Link
The lines of the program in writing have many conditons and thus have reached more than 255 characters which is the maximum number of characters allowed per line in DB classic. I believe there is a way to tell the computer to continue on the next line but I haven't been able to find out how. I tried using if/endif instead but I'm getting a "Syntax error. Nesting error" message. I'm not sure why I'm getting that error because the only line I used Endif with has an If right before it. Maybe it has to do with the program having lots of "Ifs" before and after elsewhere? If so do I need to use Endif with all the other Ifs?
Any help will be appreciated!
Back to top
Profile PM
Pincho Paxton
21
Years of Service
User Offline
Joined: 8th Dec 2002
Location:
Posted: 2nd Jul 2006 02:36
Link
The nesting error could be anywhere, you need to look for it, and sort it out.

Back to top
Profile PM Email Website
047
18
Years of Service
User Offline
Joined: 4th Jun 2006
Location:
Posted: 2nd Jul 2006 02:55
Link
But there were no errors and the program was working perfectly until one of my lines exceeded 255 characters and I had to use the IF/ENDIF just for that one line. I have only used IF/ENDIF on that one line so unless I'm not clear on what a "Syntax error.Nesting error" message implies I don't see how the error can be anywhere else other than that single line with the ENDIF at the end. On all my other lines I've used IF/THEN with no problems. As a matter of fact, if I removed the ENDIF and somehow just made that line shorter everything would be OK, maybe I should use a GOSUB instead. Could anything else trigger such an error message?
Thanks!!!
Back to top
Profile PM
047
18
Years of Service
User Offline
Joined: 4th Jun 2006
Location:
Posted: 2nd Jul 2006 06:27
Link
I was able to fix the problem. I don't know what I did but putting the ENDIF after a [TAB] somehow corrected the error. Apparently DB is picky about the formatting of the lines...
Thanks anyway Pincho!
Back to top
Profile PM
Back to top

Login to post a reply

Server time is: 2024-11-26 17:23:27
Your offset time is: 2024-11-26 17:23:27