Maptitude - http://research.umbc.edu/~roswell/maptitude.html
Unfortunately I have seen this before, but it is intermittent. I actually do
not think it's a Maptitude problem but an Excel problem. In my humble
opinion, the Excel format is the format from Hell - it has caused me nothing
but misery in many situations; I suspect that for developers it is the same
**2.
I have had problem with Excel formats in Splus, SAS, SPSS, EpiInfo, AV,
MapInfo, and Excel itself. Especially when trying to get Excel into a dbf
format.
This has nothing to do with a controlled experiment, it may be chicken
innards and tea leaves, but I find that when I want to use a program that
says it will read an Excel file, it seems to help to 1. specify a print area
and 2. Be sure the columns are wide enough that all the data can be seen.
I know that is weird, but it does seem to work.
Richard Hoskins
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
GMT -8
-----Original Message-----
From: Kjartan Stefansson [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 20, 2001 5:55 AM
To: [EMAIL PROTECTED]
Subject: Re: [Maptitude] Maptitude kills Excel file row names
Maptitude - http://research.umbc.edu/~roswell/maptitude.html
Richard Hoskins writes:
> I read in an Excel file (Office 2000) into Maptitude and I get for the
> variable names F F1 F2 F3 ... etc. not the correct variable names, and
no
> progress bar - it just appears very quickly.
...
I'm not aware of a problem like the one you describe with Maptitude
reading Excel files. In fact your description seems to indicate
that this is a rare occurrance. If you still have the problematic
file around, I would suggest you send it to Caliper's tech
support. For those rare problems that are hard to reproduce, it is
invaluable to have an input that exhibits the problem.
-Kjartan
______________________________________________________________________
To unsubscribe, write to [EMAIL PROTECTED]
______________________________________________________________________
To unsubscribe, write to [EMAIL PROTECTED]
