I just thought I'd toss in what I think is a bug on Excel's part: when
exporting sheets to dBase files (and possibly other formats that require
explicit field widths), you have to make sure your column widths in Excel
are slightly larger than required. If they're not Excel truncates data in
the columns that are too small.
This behavior is outlined in the help file. Search under dBase and, on my
version (Office 97), you'll see an entry for "When I save data in dBASE
format, some of my data is missing." It also describes having the range
"Database" set. These are important issues that, for me, are annoyances!
Alex Machinis
EMPOWER GEOGRAPHICS, INC.
1000 Executive Way
Des Plaines, Illinois 60018-1502
847/299-6952 x212 Fax: 847/299-6990
http://www.empowergeo.com
mailto:[EMAIL PROTECTED]
Note: this message and any attachments have been scanned and checked for
viruses. You may want to perform checks with your own anti-viral
software.
-----Original Message-----
From: Vince Elenko [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 29, 1999 05:33 PM
To: 'Marty DeBenedictis'; MapInfo list
Subject: RE: big excel files: scary MI behavior
I just had this problem the other day - Here's what worked for me:
Open the file in Excel and save it as a .dbf file then open the table from
MapInfo and it should work. Also, if some of your data requires a specific
number of decimal places, in Excel, got to format/cell and specify the
number of decimal places - If you don't, the decimal places will be lost in
the conversion, regardless of what you see in the spreadsheet.
Good Luck
Vince Elenko
Petrorep Resources Ltd.
-----Original Message-----
From: Marty DeBenedictis [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 29, 1999 2:05 PM
To: MapInfo list
Subject: big excel files: scary MI behavior
Greetings:
Using MI 5.01, when I import a large excel file, MI only brings in the
data for the first 32,768 records. The ugly part is that it shows the
correct record count, but every record after 32,768 is blank. Tech
Support says this is a limitation in MapInfo. Ok, but shouldn't there
be an error message or something? If you didn't look, you could end up
with some scary results. Does anyone know anything more about this? Is
there a fix in the works?
Thanks,
mdb
------------------------------------
Marty DeBenedictis
Community Mapping Assistance Project
NYPIRG
[EMAIL PROTECTED]
------------------------------------
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
