Problem: overwriting dbf file when using save as with a different name

[GoogleCodeExporter]

There seems to be a problem saving an edited table "as" a different file.
Here is the scenario using GeoDa 1.5.12:
- using Columbus, I created two new variables, standardized crime and 
standardized hoval
- these are added as the two first columns in the table
- then I select File > Save As and specify a new file name, e.g., col1
- a new file is saved as col1.gda, but the dbf, shp etc. files keep the same 
name
- as it turns out the "old" columbus.dbf file contains the new variables, which 
is
  not the desired result: the new columns should be in a col1.dbf etc file, not
  overwrite the original file (the point of "save as" is to create a different file)

Original issue reported on code.google.com by lanse...@gmail.com on 31 Dec 2013 at 8:38

[GoogleCodeExporter]

Original comment by lanse...@gmail.com on 31 Dec 2013 at 8:40

• Added labels: Milestone-Release1.6, Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

"Export" menu item is used for saving to a different file. Since it is possible 
to save current file as a database table or any other format, we need to prompt 
a dialog to let user choose both project name and new file name.

One solution is that we can merge current "Save As" (only for project file) and 
"Export" (for new datasource and new project file). 

Since "Save As" means a different file(datasource), we can change "Export 
Selected.." to "Save Selected As...".

Original comment by lixun...@gmail.com on 2 Jan 2014 at 7:46

[GoogleCodeExporter]

Use "Export" menu item for saving to a different file.
"Save" menu item is for project file and current opened datasource.
"Save As" (change to "Save Project As" ) menu item is for project file only

Original comment by lixun...@gmail.com on 11 Feb 2014 at 4:00

• Changed state: Fixed