I have a suggestion, but I'll admit I'm not 100% sure I'm right. I believe that sys_tables is an internal table generated by RBase as it is needed (correct me if I'm wrong, Razzak). If any of those tables or views have errors in them, you can get error messages as it is trying to generate the sys_tables internal table. I've often seen views that are no longer valid, they are old views and reference columns/tables that no longer exist, or they refer to variables that are not defined (something I try to avoid whenever possible). If you trace a program that has a Gateway Import in it, and RBase goes thru its long process of validating database schema before the import begins (something I frankly wish it wouldn't do), you will see error messages for any invalid views. So maybe that's creating those messages?
Karen In a message dated 9/2/2012 1:20:54 PM Central Daylight Time, [email protected] writes: > 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. >
