AFAIK, the load from filespec as ascii doesn't support collist..
We use ASCII files from other entities, however, if just dealing with RBASE
generated structure/data files, then one could use collist in the load.
Thanks,
Brent
-----Original Message-----
From: Albert Berry <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Saturday, June 23, 2001 7:46 AM
Subject: Re: Oterro 2.0 load command
>Have you tried specifically adding the column list with the USING clause?
>
>----- Original Message -----
>From: "Brent Skean" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Saturday, June 23, 2001 12:43 AM
>Subject: Oterro 2.0 load command
>
>
>> I've come across the following that I will report through RDCC:
>>
>> In RBase 6.1a (not tested in 6.5...), if I have a table that has been
>> altered and AUTOROWVER is ON, then a sys_rowver column is added. If
there
>> were 6 columns, there are now 7.
>>
>> If I have an ascii file that I wish to load into this table and the ascii
>> file has 6 fields of data, the ascii file will be properly loaded into
the
>> table.
>>
>> In Oterro 2.0, using Tango 2K as the front end with a DBMS of
>>
>> load tablename from filename as ascii
>>
>> The 6 field ascii file will NOT load into a 6 field table that has a
>> sys_rowver added onto the end (making it 7 fields). Error message of
>> incorrect number of values.
>>
>> Removing the sys_rowver from the table allows the load to proceed from
the
>> DBMS.
>>
>> Brent Skean
>> Current Solutions
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
