Hey Jim, Happy R:Labor day. Separation of variable assignments seems to be one of those learning curve issues; not as clear-cut as I thought. As to SET VAR, I've attempted to be consistent in grouping variable assignments following the advice of the "Gaining Speed with Programming Guide", which recommends: "Group similar commands ... try grouping separate SET VARIABLE commands into one SET VARIABLE where possible."
Within loops, my practice is to follow the documentation for WHILE and WHENEVER loops, which recommends: "If you issue multiple SET VARIABLE commands on a single command line [grouped?], then those variables will not be optimized. If you want to increase the speed for that loop, you should put the SET VARIABLE commands on separate lines." So we're good there. But outside of a loop, why an issue? My sloppy coding? (See my response to Razzak's Blues Clues Views). More interestingly, his enclosure within parentheses of the dotted variable in: SET VAR vTargetTable = (.vImportTable) ... rendering it into an expression, suggests that may be the ticket. Thoughts? Thanks much, Bruce Chitiea -------- Original Message -------- Subject: [RBASE-L] - Re: Error Source Mystery From: jim schmitt <[email protected]> Date: Sun, September 02, 2012 3:06 pm To: [email protected] (RBASE-L Mailing List) Hi, Bruce: See if this helps by making each line separate: SET VAR vimporttable = 'pksimport' SET VAR vtargettable = .vimporttable Jim Schmitt From: Bruce Chitiea <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Sunday, September 2, 2012 2:19 PM Subject: [RBASE-L] - Error Source Mystery All: I'm up and running, so this is for understanding only. For reasons obscure and unclear, the following code produces two errors, interrupting TRACE processing: SET VAR + vimporttable TEXT = NULL, + vtargettable TEXT = NULL, + vsystablecount INTEGER = NULL SET VAR + vimporttable = 'pksimport', + vtargettable = .vimporttable SELECT COUNT (*) + INTO vsystablecount IND iv1 + FROM sys_tables + WHERE sys_table_name = .vtargettable "ERROR-I/O Problems-Check for a full disk. (2009)" "ERROR-Database files are out of sync. (2520)" Hmmm. 1. The drive has multi-gigabytes free; 2. Autochk shows no errors; 3. RBSYNC reports all four RX? files synchronized; 4. R:Scope finds no errors; 5. PACKing the database doesn't affect it; 6. CHKDSK (w/admin permissions) reports no disk errors. What, then, would trip these particular error messages? Thanks Bruce
