I would put the AS ASCII back in and take out the FILL option. I assume your file is an asci delimited file
Troy ===== Original Message from [EMAIL PROTECTED] at 11/13/01 9:46 am >G-Day all > >I need to ping the GURU's on this one.. > >Running this code: > >SET NULL -0- >LOAD fouro1k + >FROM &vg_chrfilepath USING clockno,fro1k_wages,fro1k_current,+ >check_date,hours_worked ;NOCHECK;FILL >SET VAR var_interr = .errvar >IF var_interr = 0 THEN > PAUSE FOR 1 USING 'Technituft loaded' AT CENTER CENTER >ELSE > PAUSE FOR 1 USING 'Loading Error ' at center center >ENDIF >SET NULL ' ' > >When this runs at run time... the PAUSE saying Loading >Error pops up... > >During trace errvar and var_interr stay at 0 (zero). > >The data is loading which is what's important here.. >but I would like to be able to count on the error >variable to tell if it did.. > >If all else fails I will go to using a SELECT to see >if the data go loaded, but I should have to.. > >Has anyone seen this before..? > >By the way, when I was running this code in version >6.1a I was doing a >LOAD fouro1k + >FROM &vg_chrfilepath AS ASCII... and it was working fine.. >There are two more columns that the amount of fields >that we are loading in. >Now that we went to 6.5++ I had to modify the code... >Upon a more detailed look at the Syntax I almost see why, >but there isn't a real good explanation of what parts of >the commands work with the new AS ASCII... or not? > >Jim Limburg
