systems extents. Does a zoom extents zoom way out? Turn Qtext on and zoom
extents there may be a null text object out there in wonderland.
"monkey5672" wrote in message news:firstname.lastname@example.org...
Checking my acadmap.log file ... there are a bunch of entries from this
morning, all pretty much alike. The only difference among them is the Handle
ID. Example below:
AutoCAD Map Error : 1 - Can't perform datum conversion.
AutoCAD Map Error : 1902 - Can't transform object.
LWPOLYLINE - handle A1E
I couldn't begin to explain why, but its a pretty annoying occurance.
I'd imagine the FDO connections work better in 2009. Anyone else have similar experiences?
Thanks, -jason m.
We were having the same issue "Export did not succeed"
We successfully used MAPEXPORT4 but couldn't select all of the object data from multiple tables.
The very next command we used was the standard MAPEXPORT. We chose all of the data we initially wanted and it worked.
I guess we had to teach Map how to do it the old way before it would have the confidence to do it the new way?!?!
Same problem here. "Export did not succeed."
Turns out the issue was trying to export to a folder that was too crammed with other files. Created a new folder, exported to that, and it worked.
I tried re-installs of all my Autodesk and ESRI products but couldn't get it working again. I finally had to do a complete, clean uninstall of all ADESK stuff and then put Map2011 back on to get my shape export back. It seemed a little heavy handed to me but in a mixed Autodesk/esri shop I had to get it working again.
After recently installing Map3D 2012, "Did not Succeed" happened to me.
Thanks to seeing a post on this thread, I tried creating a new folder with nothing in it... then it magically worked!
Lol ToddC, same here. worked fine once i went to a new folder.
Using Civil 3d 2012, had the same problem. Folder cluttered with other shape files can't be exported to for some reason!! what the hell.
Additionally mapexport sucks at exporting closed polygons!