I'm not sure what you mean by "contend with nulls". And I'm not sure what you
want.
This KB article describes what's happening--it goes back to Excel 5.0, so it's
pretty old.
http://support.microsoft.com/default.aspx?scid=77295
Column Delimiters Missing in Spreadsheet Saved as Text
Geri wrote:
>
> So, if I'm importing this into a database I then have to contend with Nulls?
>
> I know this worked before without having to go through populating blank
> fields .... any idea what changed? -- or is this a bug? That was the beauty
> of Excel - you could get a "clean" .csv file but I guess all good things must
> pass at some time.
>
> thanks,
>
> Geri Smith
>
> "Dave Peterson" wrote:
>
> > Put something in that last column.
> >
> > Select the last column
> > edit|goto|special|select blanks
> > type
> > =""
> > hit ctrl-enter
> >
> > Now you have something in those cells, so each line will get the commas.
> >
> >
> >
> > Geri wrote:
> > >
> > > I have a spreadsheet that's 625 rows x 11 columns the first 4 columns are
> > > populated in all rows. The problem is that the remaining 7 columns have no
> > > data in them but need to be imported by another program showing a "null" in
> > > those columns.
> > >
> > > Try as I might, Excel will only put commas at the ends of the first 16
> > > records after which it ceases to do this. We get the message that Excel "may
> > > contain features that are not compatible with CSV". When the file gets to
> > > the other end, needless to say, it's pretty much useless. How do I get Excel
> > > to recognize all the cells, regardless?
> > > --
> > > Geri Smith
> >
> > --
> >
> > Dave Peterson
> >
--
Dave Peterson
Bookmarks