Thanks, but the only thing I could do was recreate indexes and tables with smaller names. Do we know what is the rule for names given to tables. I mean the max size we should use?
"Mark Sires" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Directly from the documentation the cause of a <SUBSCRIPT> error: > A subscript has an illegal value or a global reference is too long. If a > global reference is too long, then either (1) the encoded length of an > individual subscript exceeds 255 bytes or (2) the sum of the encoded lengths > of the following items exceeds 512 bytes: the length of the global name; the > lengths of all subscripts; the number of subscripts; the number of numeric > subscripts; and the number of negative numeric subscripts. > > Looking at the %BLSOOP1 line tags that several of my classes have generated, > the checking for illegal (null) subscripts looks pretty solid, so I would > suspect that the length is being exceeded on some index entry. You could > eliminate nulls being the problem by changing the configuration > manager->advanced->objectscript->Null Subscripts enabled from No to Yes, > then retry the rebuild. If it doesn't error, then the null checking is > failing, and it should be reported to InterSystems. > > Otherwise, if one or more of your indexes is using very long properties, or > many small properties (and it's not a bitmapped index), that is probably the > problem. > > Mark > > > "Denver Braughler" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > RJH wrote: > > > Denver wrote: > > > > RJH wrote: > > > > > Can anyone tell me what the following error means...? > > > > > <SUBSCRIPT>%BSLoop1+4^pkgAssessment.QstionsCtgrySction.1 > > > > Can you do this?: > > > > w $t(%BSLoop1+4^pkgAssessment.QstionsCtgrySction.1) > > > Yes I did, but I get nothing on the terminal screen. > > > > That suggest that the source code for pkgAssessment.QstionsCtgrySction.1 > is missing or not in the namespace where you tried it. > > > > Do you have a copy of the terminal output? > > > > How about?: > > ZL pkgAssessment.QstionsCtgrySction.1 ZP > > > > > is my table name too long? > > I hope not. > >
