Thanks Robin, From which you've deduced they are "all" significant? I really should have done some such similar thing myself, but I know you guys like to feel "used"??? No, I mean, you like to participate! Thanks, Joe PS -- I still liked the way it was spelled out in black & white in FBII. Oh, and how come you're not using the soft return? Option/L, or can that be done "inside" VARS? Another ponderable? Robin wrote: > >> "length [can be] up to 240 characters. Only the first 15 are significant." > >> > >> I couldn't find a corresponding statement in the FBIII ref. (I've got 1.4.) > > > > Geeze, Lucy - thanks! > > > > I knew it was there somewhere. Now, I need to know - do these > > same limitations apply to FB^3? I'm trying to list FB^3s limitations > > and, as best I can determine, there is no equivalent to FBII's > > Variable Name Rules in FB^3's documentation. Help anyone? > > The FB^3 Reference Manual p7 says this: > > An identifier is a name that you make up to identify something in your > program. In FB^3, identifiers are used to name the following kinds of > things: variables (see Appendix B); arrays (see below); user-defined > functions (see the LOCAL FN , LONG FN etc. statements); user-defined data > types (see the #DEFINE and BEGIN RECORD statements); record fields (see > the BEGIN RECORD and DIM statements); symbolic constants (see the > 3Constant declaration2 statement). In FB^3, an identifier can have any > length up to 245 characters. It must star with a letter; its subsequent > characters can be any combination of letters, numeric digits, and underscore > characters ( _ ) (symbolic constant names should not contain embedded > underscores). Identifiers which represent... > > This doesn't actually say how many of the 245 are significant, from which I > deduce (?) they all are! Furthermore, being a scientist, I did an > experiment. If you do a test compile on the following (you'll have to > re-merge the split variable names), you will find that the second "dim a" is > marked as a redefined variable error, but the second version of my very long > variable (245 chars) is not. Elementary, my dear Dr Watson. > > defint a-z > end globals > > clear local > dim a > dim a > dim > thisisareallylongvariablenamelikeitmustbeover50characterslonginfacttohereiti > ss80thisisareallylongvariablenamelikeitmustbeover50characterslonginfacttoher > eitiss80thisisareallylongvariablenamelikeitmustbeover50characterslonginfactt > ohereitiss80four1 > dim > thisisareallylongvariablenamelikeitmustbeover50characterslonginfacttohereiti > ss80thisisareallylongvariablenamelikeitmustbeover50characterslonginfacttoher > eitiss80thisisareallylongvariablenamelikeitmustbeover50characterslonginfactt > ohereitiss80four2 > local fn Tester > end fn > > WINDOW 1,"",(0,0)-(500,400),_dialogFrame > tron break > > fn Tester > > do > until fn button