News Article

VistaDB 2.0 (Beta 3) Preview 2 available

May 18th, 2004

While we work on getting the full Beta 3 released, we have posted a a new Preview 2 build. You do not need VistaDB 2.0 (Beta 2) to install, nor Preview 1 to install this build.

Download Beta 3 Preview 2 from here.

Preview 2 Release Notes

• Fixed running SQL in Data Builder.
• Fixed an AV when creating a 2nd query.
• Fixed re-using the connection with different query parameters.
• Fixed error in WHERE expression that involved Double data types.
• Fixed "Correction of disposal of SQL objects from the provider". This issue caused random problems when many query objects were created but not freed properly.

After downloading, open the zip and read the README.TXT file before unzipping all the files. The readme contains installation instructions.

Known Issues (Preview 1&2)

• 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.
• Issue with DateTime params, related to converting "ticks" to Int64.
  The fix will be in the full Beta 3 release.
• Support for Currency params is missing.
  This fix will be in the full Beta 3 release.
• VarChar columns are returning padded white space on the right.
  This fix will be in the full Beta 3 release.
• 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.
  We are investigating this.

Trouble Shooting (Preview 1&2)

• 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.