News Article

VistaDB 2.0 (Beta 3) Preview 3 available

May 23rd, 2004

While we work on getting the full Beta 3 released, we have posted a a new Preview 3 build. This is a full .MSI installer build so you do not need any previous version of VistaDB in order to install this build.

Download Beta 3 Preview 3 from here.

Preview 3 Release Notes

• New .MSI installer for this build.
• New History commands for running dynamic SQL in Data Builder
• New Reference Help files now included with this build
• Fixed issue with DateTime params, related to converting "ticks" to Int64.
• Fixed support for Currency params.
• Fixed VarChar columns to ruturn trimmed padded from data.
• Fixed Character columns to return fixed, padded characters (fixed to the size of the defined column)
• Fixed Data Builder Relationships dialog

Known Issues

• CommandBuilder does does not take extra steps to manage reserved words.
  This fix will be for RC1.
• SQL param names may not conflict with Reserved Words. For example:
  SELECT * FROM test WHERE ([password] = @password) This SQL is invalid because "password" is a reserved word.
  SELECT * FROM test WHERE ([password] = @pwd)
  This SQL is valid. The fix will be in RC1.
• VistaDB DataAdapter Designer. When a Dataset is created using the DataAdapter verb 'Create dataset...', various new info is not being generated (e.g. Primary Key, Readonly, etc).
  This fix will be in the full Beta 3 release.
• VistaDBTable.ColumnName() does not work on a Windows 2003 Server. It works fine on Windows 2000 and XP.
  This fix will be in RC1.

Trouble Shooting

• If you are unable to install VistaDB into your Visual Studio 2003 IDE and/or are missing the "Add/Remove Items" when you right click in the Toolbox, then you are most likely not using the latest version of Visual Studio and will need to get the update. The correct version of Visual Studio is 7.1.3088 and for the .NET Framework is 1.1.4322
• Change all references from "DBType" enumerator to "VistaDBType". Careful! DBType calls another constructor that expects param name and value, not param and type as does VistaDBType.
• Check the Reserved Words list in the help file. Column names that conflict with reserved words must be enclosed in brackets when being accessed from SQL.
  e.g. SELECT firstname, [password], [begin] FROM TEST
  "password" is a reserved word, and therefore must be enclosed in [].
• Do not connect to a .VDB database while it is open in Data Builder. Data Builder opens databases in exclusive mode and therefore prevents other applications from accessing the database.
• Use "@" instead of ":" for defining parameters in SQL. The "@" must also be included when creating or accessing params too.
  e.g.
  

  'VB.NET version ------------------------------------------
  conn = New VistaDB.VistaDBConnection("Test.vdb")
  conn.Open()
  daTest = New VistaDBDataAdapter
  daTest.SelectCommand = New VistaDBCommand
  cmdSQL = "SELECT * FROM test WHERE (state = @state and city = @city)" daTest.SelectCommand.CommandText = cmdSQL
  daTest.SelectCommand.Parameters.Add("@state", VistaDBType.Character)
  daTest.SelectCommand.Parameters.Add("@city", VistaDBType.Character)
  daTest.SelectCommand.Parameters(0) = "CA"
  daTest.SelectCommand.Parameters(1) = "San Diego"
  daTest.InsertCommand.ExecuteNonQuery
  
  
  // C# version ------------------------------------------ conn = new VistaDB.VistaDBConnection("Test.vdb");
  conn.Open();
  daTest = new VistaDBDataAdapter();
  daTest.SelectCommand = new VistaDBCommand();
  cmdSQL = "SELECT * FROM test WHERE (state = @state and city = @city)";
  daTest.SelectCommand.CommandText = cmdSQL;
  daTest.SelectCommand.Parameters.Add("@state", VistaDBType.Character);
  daTest.SelectCommand.Parameters.Add("@city", VistaDBType.Character);
  daTest.SelectCommand.Parameters(0) = "CA";
  daTest.SelectCommand.Parameters(1) = "San Diego";
  daTest.InsertCommand.ExecuteNonQuery();

Many thanks for being patient while we get this milestone build released. Expect a full Beta 3 release any time now.