One response to all. Thank you! **** Pat:
>> Did you try inserting a null column after the autonum column of the >> opcashbalance table before import? [bac] No. **** Gary: >> What does the date format look like in csv file? [bac] The CSV file is created as a [Move Sheet to New Book] from Excel 2007, [Save As] MS-DOS CSV, date format set as MM/DD/YYYY with no leading zero. I've had this process working reliably in other import operations, hence the ??. Through experimentation with Excel and CSV imports over a period, I determined to my satisfaction that the first date format option offered by Excel (2007 is what I have) is the most bullet-proof for creating and importing CSV files: '*3/14/2001' **** Dennis: >> Have you tried syntax #3 of the LOAD command to get your data into the >> table? You can specify what columns are populated from the CSV file [bac] No. Hadn't even occurred to me. I'll certainly check that out. **** Jason Kramer: >> I am running 9.5.2.11115 x64 on Windows 7 Ent x64, but I get the same result >> you do. I created an import specification file (.rgw file) and that solved >> the problem. You may have to edit the rgw file to account for the different >> file path to the csv file on your system. I had success using this command: >> GATEWAY IMPORT CSV gway_cashbal.csv APPEND opcashbalance OPTION AUTONUM >> ON|SPECIFICATION_FILE_NAME gway_cashbal.rgw >> You may also have to edit the path to the RGW file (I highly recommend that >> you keep it in your DB directory), and the path to the import file. I just >> put the import file in my DB directory to simplify things. [bac] Following your lead, I ran the Gateway module from the interface (which worked), saved it as 'gway_cashbal.rgw', deleted the import, ran with the RGW file from the R:Prompt. That worked too. [bac] So ... why not 'natively' from the R:Prompt? Why not with 'ADD_MAPPING'?? Hmm.
