UweKeim / ZetaResourceEditor

Free multilingual, parallel .NET resource file editing

Home Page:https://www.zeta-resource-editor.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Export to different worksheet with cryptic names fail

ArneD opened this issue · comments

Hi,

We encountered the following error when exporting each file group to different sheet and using the option 'use cryptic names'.
Seems the GUID generation is not correct.

Edit: After closing and re-opening the program, it works.


-----------------

A DataTable named '00000000-0000-0000-0000-0000...' already belongs to this DataSet.

-----------------

at System.Data.DataTableCollection.RegisterName(String name, String tbNamespace)
   at System.Data.DataTable.set_TableName(String value)
   at ZetaResourceEditor.RuntimeBusinessLogic.ExportImportExcel.Export.ExcelExportController.doProcess(PreparedInformation preparedInformation, BackgroundWorker bw, Int32 fileGroupsLength, ICollection`1 savedFiles) in c:\P\ZetaResourceEditor\Source\RuntimeBusinessLogic\ExportImportExcel\Export\ExcelExportController.cs:line 451
   at ZetaResourceEditor.RuntimeBusinessLogic.ExportImportExcel.Export.ExcelExportController.Process(BackgroundWorker bw) in c:\P\ZetaResourceEditor\Source\RuntimeBusinessLogic\ExportImportExcel\Export\ExcelExportController.cs:line 304
   at ZetaResourceEditor.UI.ExportImportExcel.ExcelExportWizardForm.progressBackgroundWorker_DoWork(Object sender, DoWorkEventArgs e) in c:\P\ZetaResourceEditor\Source\Main\UI\ExportImportExcel\ExcelExportWizardForm.cs:line 749
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

DuplicateNameException
{
	Message="A DataTable named \\'00000000-0000-0000-0000-0000...\\' already belongs to this DataSet.",
	Data=
	[
	]
,
	InnerException=null,
	TargetSite=RuntimeMethodInfo: RegisterName,
	StackTrace="   at System.Data.DataTableCollection.RegisterName(String name, String tbNamespace)\\r\\n   at System.Data.DataTable.set_TableName(String value)\\r\\n   at ZetaResourceEditor.RuntimeBusinessLogic.ExportImportExcel.Export.ExcelExportController.doProcess(PreparedInformation preparedInformation, BackgroundWorker bw, Int32 fileGroupsLength, ICollection`1 savedFiles) in c:\\P\\ZetaResourceEditor\\Source\\RuntimeBusinessLogic\\ExportImportExcel\\Export\\ExcelExportController.cs:line 451\\r\\n   at ZetaResourceEditor.RuntimeBusinessLogic.ExportImportExcel.Export.ExcelExportController.Process(BackgroundWorker bw) in c:\\P\\ZetaResourceEditor\\Source\\RuntimeBusinessLogic\\ExportImportExcel\\Export\\ExcelExportController.cs:line 304\\r\\n   at ZetaResourceEditor.UI.ExportImportExcel.ExcelExportWizardForm.progressBackgroundWorker_DoWork(Object sender, DoWorkEventArgs e) in c:\\P\\ZetaResourceEditor\\Source\\Main\\UI\\ExportImportExcel\\ExcelExportWizardForm.cs:line 749\\r\\n   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)\\r\\n   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)",
	HelpLink=null,
	Source="System.Data",
	HResult=-2146232030
}```

Thanks, I'll take a look.

I've tried to reproduce it but unfortunately until now I don't manage to create this error.

Could you please help me by:

  • showing me step-by-step screenshots of the export wizard and its values. -and/or-
  • sending me an example project to generate the error.

Would be very helpful.

It worked after restarting the program.

However, I could reproduce the error with the following steps:

  • Create new project
  • Add existing file group to project
  • Add atleast 2 existing file groups
  • Export to Excel
  • Select all the files and all the languages
  • Select 'Export each file group into seperate work sheet'
  • With the following options:
    image

Hope this helps!

Seems that you have unsaved items. The export wizards seems to not check that.

I've just published a new version (2.3.0.5), that could fix this, although I still don't fully understand what could lead to the error condition.

Maybe you could give the new setup a try.

Seems to be working now!