Import Problem (AREV Specific)
At 03 JAN 2000 11:27:56AM Frank Noren wrote:
Starting today, Jan 3, my import will not work. It seems to set the size lock and places every record into group 1….then I reach the maximum size for key ids.
Does anyone have any ideas ??
At 03 JAN 2000 01:24PM Warren wrote:
The dreaded Y2K bug???
Sizelock should only be set to "1" with CREATEFILE/MAKETABLE so you got me there too!
What happens if you clear the target table manually first and then *don't* let IMPORT clear the target file?
At 04 JAN 2000 08:22AM Larry Wilson wrote:
You say it sets the sizelock, but don't say what it sets it to. Probably, the sizelock is getting set to GE 2 which would preclude file expansion.
To make copies more efficient, before clearing the file, set the sizelock to 1, clear the file and then do your copy. You may then either set the sizelock to 0 or 1 (unless it's a temp file that may shrink, I leave all sizelocks at 1 and check them often).
tardis_systems@yahoo.com