On 1/3/06 7:18 AM, "Bill" <[EMAIL PROTECTED]> wrote: >the "\" (...) Can't be > used to split a string.
There is a very good reason for this convention: This allows you to use any words you want in a text string and they will not be confused with commands. Imagine wanting to use the word "repeat" in a paragraph that the user will read, but the compiler said 'too, bad, it is a reserved word'. And all the others = "it, for, when, put, end, while, format, folder, file, into, ........" Basically, the compiler is digesting variables, assignments, repeat loops, reserved words, etc, but *suspends* this while scanning a text string, therefore, it does detect special structures like end-of-command-line. HTH Jim Ault Las Vegas On 1/3/06 7:18 AM, "Bill" <[EMAIL PROTECTED]> wrote: > I always wondered why sometimes the "\" character didn't work. I thought it > was me and I just started making extremely long lines in my code. Can't be > used to split a string. Geez. I guess there is a complex reason for that > related to hexadecimal inputs through the hyperspatial tuning of the > dilithium crystal memory stacks or some such. > > > On 1/2/06 4:41 PM, "Jim Ault" <[EMAIL PROTECTED]> wrote: > >>> two lines it dies. I've tried using the / with no luck. >> The correct character is "\" >> >> Not sure what you are doing specifically, but remember, the "\" cannot be >> used to split a string: >> NO: >> put "the lazy brown dog jumped \ >> and bit the mailman" into neverHappened >> >> Yes, even in the multi-line message box: >> put " the lazy mailman bit " & \ >> "the brown dog" into newsAtSix >> >> >> Jim Ault >> Las Vegas >> >> On 1/2/06 12:34 PM, "Jeff Honken" <[EMAIL PROTECTED]> wrote: >> >>> Is there any way to have a SQL statement on multiple lines. My code >>> works great if the statement is all on one line but once I try to go to >>> two lines it dies. I've tried using the / with no luck. Here's a very >>> cut down version of what I'm trying: >>> >>> --> CONSTRUCT SQL >>> put "CREATE TABLE Provider >>> (ProvAutoNo INTEGER PRIMARY KEY, ProvActive text)" into tSQL >>> --> EXECUTE SQL >>> put revdb_execute(gConID,tSQL) into tList >>> >>> The Provider table is actually very large. >>> >>> >>> _______________________________________________ >>> use-revolution mailing list >>> use-revolution@lists.runrev.com >>> Please visit this url to subscribe, unsubscribe and manage your subscription >>> preferences: >>> http://lists.runrev.com/mailman/listinfo/use-revolution >> >> >> _______________________________________________ >> use-revolution mailing list >> use-revolution@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-revolution > > | | | > )_) )_) )_) > )___))___))___)\ > )____)____)_____)\\ > _____|____|____|____\\\__ > -------\ /--------- http://www.bluewatermaritime.com > ^^^^^ ^^^^^^^^^^^^^^^^^^^^^ > ^^^^ ^^^^ ^^^ ^^ > ^^^^ ^^^ > > 24 hour cell: (787) 378-6190 > fax: (787) 809-8426 > > Blue Water Maritime > P.O. Box 91 > Puerto Real, PR 00740 > > > > _______________________________________________ > use-revolution mailing list > use-revolution@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution