Here is what is thrown into my log file when the font exception occurs.
2006-07-14 08:01:28,432 [FATAL][Imaginet.Foundation.Log]- Exception: Imaginet.Foundation.Exceptions.ImaginetException
No additional info.
AppDomain Name: TGS.MAS.exe
Occurred at: 8:01:28 AM
Exit Code: 0
OS Version: Win32NT - 5.2.3790.0
Stack trace: Inner Exception: Font 'Monotype Corsiva' doesn't support style 'Regular'.
Stack trace: at TGS.MAS.ucMappingControl.LoadSpreadSheetWithFile(String p_FileName) in C:\Projects\TGS\MAS\_Current_Iteration\TGS.MAS\UserInterface\Mapping Wizard\ucMappingControl.vb:line 314
at TGS.MAS.ucMappingControl.MoveTo(Guid p_MapId) in C:\Projects\TGS\MAS\_Current_Iteration\TGS.MAS\UserInterface\Mapping Wizard\ucMappingControl.vb:line 545
at TGS.MAS.ucMappingControl.NewMap() in C:\Projects\TGS\MAS\_Current_Iteration\TGS.MAS\UserInterface\Mapping Wizard\ucMappingControl.vb:line 971
at TGS.MAS.frmMappingWizard.mnu_NewMap_Click(Object sender, EventArgs e) in C:\Projects\TGS\MAS\_Current_Iteration\TGS.MAS\UserInterface\Mapping Wizard\frmMapWizard.vb:line 237
at System.Windows.Forms.MenuItem.OnClick(EventArgs e)
at System.Windows.Forms.Command.DispatchID(Int32 id)
at System.Windows.Forms.Control.WmCommand(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) -[Imaginet.Foundation.Logging.Logger.LogFatal(C:\Projects\Imaginet\Foundation\_Current_Iteration\Imaginet.Foundation\Logging\Logger.cs:543)]
About the loading time issue:
We have run our application from VS2003 on 4 machines here, and they all take a really long time to load certain files. The same computers running the same application, but outside of VS2003, load the files in a reasonable amount of time.
I'm just speculating here, but I think it may have something to do with how the control handles formulas that fail due to a divide by zero error. In the files that we are loading with the long load times, there are alot of cells that contain cells with a formula that evaluates to a divide by zero error, simply because they are template files and don't contain the data to correct the divide by zero error.
Here is an example of one of the formulas:
$Z$14 is blank, which is probably what is causing the divide by zero error.
There are roughly 60 cells containing similar functions to this one.
Our client hasn't provided us with a sheet that has been populated yet, so I don't know what the loading times would be like if the sheet was properly populated.
Hope this helps with your investigation of the issue.