Don't know if the content of this, my post, applies to your situation,
too.
I write it anyway, maybe it
-) helps you
-) helps someone else
-) someone else has information that I'm not aware of
What I noticed when trying to use the MAPEXPORT dialog version to
create SHP files the result were empty (zero byte) files.
The weird thing was, the object highlight to preview the to be exported
objects (loupe symbol) worked and showed the chosen objects correctly.
So no fault with selection criteria.
Not being afraid of command line usage, I tried the same via the
command line version _-MAPEXPORT and guess what, it created the correct
files with all the data in.
This difference in behaviour between dialog and commandline version
happens on 1 machine with Win2K SP2 (I don't care for MS "security
updates", I have a Linux firewall and don't use Outlock or IE) with
MAP5 (LDD3), MAP6 and MAP7 (LDD 2K4)
Tried in MAP5, didn't work, installed MAP6, still didn't work,
installed 2K4, same results.
The same file exports via MAPEXPORT dialog without problems on my
laptop in (XP, SP1, MAP5 (LDD3)).
Clients reported that the problem did arise with MAP6, but this doesn't
conform to my experiences, as it didn't work on my machine in MAP5
either.
It seems, that an install of a newer version doesn't cure the problem
if it is "on the system". I guess some commonly used files in "program
files/autodesk shared" or registry entries are messed up, everything
else (as far as I've tried on this machine...) works well. Reinstall
had no effect whatsoever.
On the laptop I don't want to install MAP6 or 2K4 just to try if the
problem arises then...
I tried transferring the FME part of the shared directory from the
working machine to the other but that had no influence on the
behaviour. It must be something else that obviously I haven't found yet.
Now I have and use some simple scripts to automate the export task via
_-MAPEXPORT, that way it works.
I would be interested to know if you also get it to work with
-MAPEXPORT.
--
ruul