I'm scratching my head here, and hope someone can point out what I'm doing wrong.?ÿ For many years I've imported comma-delimited ASCII coordinate files (PNEED) into my Surveyor+ DC without trouble, until a few days ago.?ÿ Now the DC displays the points -- apparently correctly -- in the import dialog, but when I execute the import it doesn't load any of them and displays the message "IDs incompatible with the CRD type."?ÿ I haven't changed the export workflow that generates the points, and I'm using the same thumb drive I've used successfully for several years.?ÿ Looking at the ASCII file I can't find anything amiss.
Any ideas?
I have been doing the same for years and never had that issue.?ÿ I would first check to make sure the default settings in your DC for importing the files to make sure they have not been inadvertently changed.?ÿ A .csv file is just that but I have seen issues when a non numeric character got included in the file.
?ÿ
@hi-staker Similar.?ÿ I'm running v5 0, if that matters.
I tried rebooting, and I tried first copying the file to the DC hard drive.?ÿ Still no go.
I can get by okay by creating the CRD file on my desktop first, but the import failure bit me last week while in the field, so is like to get it sorted out.
Whoops -- I just saw the problem while uploading that image!?ÿ I have the format set to spaces instead of commas.?ÿ Doh!
@jim-frame Maybe try saving your export file as a .txt instead? That is what we save all of our import/export files as. Might be worth a try....
BTW, the version I show above is from 6.08, in case you were wondering.
@jim-frame It's always the simple things that bite you in the ass!
Opening the ascii file in Excel sometimes makes a doubled comma or stray alpha character evident.?ÿ
If that doesn't help I'd delete the file type definitions and rebuild them from scratch at both the export and import end.?ÿ