BusinessLayerException
 The CurrentRow could not be evaluated because the CurrentRowIndex is out of range.  Business object record count: 0.  CurrentRowIndex: -1.

Source     : MicroFour StrataFrame Business

Stack Trace:
   at MicroFour.StrataFrame.Business.BusinessLayer.get_CurrentRow()
   at MicroFour.StrataFrame.Business.DBEFileGroupsBO.get_fg_pk()
   at MicroFour.StrataFrame.Data.TableProperties..ctor(Int32 ProfilePK, String DatabaseName, Int32 DatabasePK, Int32 TablePK)
   at MicroFour.StrataFrame.Data.ProfileEditorDialog.ShowTableProperties(Int32 TablePK)
   at MicroFour.StrataFrame.Data.ProfileEditorDialog.cmi_Profile_AddTable_Click(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

The framework is entirely case sensitive so you will not have any issues there.  But you are right in the fact that there are some tests that need to be changed to respect case and we are actually aware of this.  Thanks for your input and we will definitely look at this.  Thanks!

Trent:

Responding to this one poses a challenge from the tact standpoint. If I understand your response correctly, then the Framework itself is case sensitive. The problem may be that there is something in the DDT that is not respecting case-sensitivity. Do I understand that correctly? The reason that I'm asking is that there must be something in the DDT that is not case-sensitive, because literally all I had to do was disable case sensitivity on the StrataFrame tables, and the DDT started working. It imported the fields in my table (previously, it only identified the table). There is still no Stored Procedure import, but I'm not sure that is supported in this version.

Regards,

Flavelle

I just left out the words DDT above.  We already aware that there are some case-sensitivity issues that need to be addressed in the DDT.  On the forum when we refer to the framework, this does not include the DDT and vice-versa.  If we say "StrataFrame" then the context will determine what is inclusive in the conversation.  I appologize for any confusion...in short, you are right, there is an issue with case-sensitivty in the DDT that we are already aware of.  Thanks for your input.

Trent:

Thanks - that now makes sense. In the meantime, a workaround is to remove the case-sensitivity from the StrataFrame databases in the SQL installation - you might want to add this in the readme.

Flavelle