The most successful method I have used of late is to got to the excel spreadsheet. Highlight the rows and columns you want to export, including the column titles. Ctrl-C to copy the data. Go to access, open a new db and paste the data. You will be asked if you want the first row to be column names, say yes. A table will be created, which you can modify to your hearts content. Change date/time columns to text so they will export to R:Base correctly. "Save as" will give you an option to export. Follow your nose to export as CSV with the proper quotes, and you will have a useable CSV. With a little trial and error you will get the procedure worked out.
-- Dennis McGrath mailto:[EMAIL PROTECTED] -- Productivity Tools for R:Base Programmers http://www.enteract.com/~mcgrath/dennis -- Full time consultant with: SQL Resources Group Steve Hartmann Oak Park, IL mailto:[EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ian Chivers Sent: Tuesday, October 09, 2001 3:41 AM To: [EMAIL PROTECTED] Subject: Re: The Data Conversion from Hell i've had difficulties in the past with using gateway. what i found to be most reliable was the suggestion made by a number of people to use load table as filename as ascii from the r prompt. i make sure that the file is comma separated with quotes. hope this helps. On Mon, 8 Oct 2001 13:38:52 -0500 Texmaster Express <[EMAIL PROTECTED]> wrote: > Good afternoon. > > I'm still working on the data conversion routine from Hades. I've decided to > use the Gateway command since it seemed to work once before. I've saved my > Excel file to an XLS3 format (am using Excel 2002) and run the command: > > gateway import xls3 ords.xls replace orders > > I've also tried a variant of the above, > > gateway import xls3 ords.xls create x > > In each instance, R:Base returns the error message: > > Cannot import a table with 0 columns > > I've checked my source table in Excel and it reads just fine. I've also > checked to be sure I have an equal number of columns. > > I've also tried saving the file as a dbf, attaching it and projecting it, > but the Excel file has 169 columns, and the dbf file will only allow 128. > > Any suggestions? (Besides convincing our software company to use Oterro, > which I've already tried) > > Dan > -- Ian [EMAIL PROTECTED] Home page http://www.kcl.ac.uk/kis/support/cit//fortran/ comp-fortran-90 home page http://www.jiscmail.ac.uk/lists/comp-fortran-90.html
