From The Oxygene Language Wiki

This is a General topic
Feel free to add your notes to this topic below.

Changes and Resolved Issues in the May 2010 Release (4.0.23)

Oxygene Compiler and Related Technology

The complete list of changes and enhancements to the compiler and IDE integration can be found on the RemObjects Software Change Logs page.

Changes and Resolved Issues in the August 2009 Release (3.0.21)

Oxygene Compiler and Related Technology

The complete list of changes and enhancements to the compiler and IDE integration can be found on the RemObjects Software Change Logs page.

Changes and Resolved Issues in the May 2009 Release (3.0.19)

Oxygene Compiler and Related Technology

The complete list of changes and enhancements to the compiler and IDE integration can be found on the RemObjects Software Change Logs page.

Changes and Resolved Issues in the February 2009 Release (3.0.17)

Oxygene Compiler and Related Technology

The complete list of changes and enhancements to the compiler and IDE integration can be found on the RemObjects Software Change Logs page.

Install/Uninstall

If you uninstall the Feature Pack when a database connection exists and terminate Visual Studio, when you restart Visual Studio, the connection appears to still exist. However, the connection is not functional. If you attempt to expand it, you get an error. You also get an error if you attempt to create another connection, which is as designed since the Feature Pack contains the database support.

To workaround this problem, remove the connection by right-clicking the connection in Server Explorer and click the Delete menu item. Also, if you delete all connections before uninstalling the Feature Pack, you won't see this problem.

This is the correct behavior. The connection can be reused upon reinstallation, no workarounds required. Remove the connection if you no longer need it.

International

For example, if a table in a Blackfish SQL or MSSQL database contains International characters, adding the data to a DataGridView on a Windows Form causes an error that can crash Visual Studio. This problem occurs only if you add the data source by using the task dropdown combo box for the DataGridView component. The BindingSource component cannot be linked to any tables that contain International character fieldnames by using the Properties window. The BindingSource component must be set programmatically in the Source page (such as bindingSource1.DataMember:= 'tableName';), which then gets updated and reflected on the Design tab. This problem does not occur if the table is dropped from the data source window.

This problem could not be reproduced.

IDE

Help files now ship with the product. Pressing F1 on an item displays the appropriate help topic in the Help Viewer.

For instance, create a new Windows Application, add a button, and double-click the button. In the code editor window, add a new class above the form declaration in the type section. When you click the Design tab, you get an error message and the design area is not displayed. You cannot access the design area until you remove the class definition.

This is as designed. The MainForm class needs to be the first class in the unit for the designer to work. Otherwise, the designer does not know which class to design, since, in theory, there could be several classes of designable type there.

If you get an error while adding a datasource, a workaround is to install the following service pack:

Microsoft SQL Server Compact 3.5 Service Pack 1 and Synchronization Services for ADO.NET version 1.0 Service Pack 1 for Windows Desktop from here

The Add | New Data Source wizard allows you to add a database and a data connection for a Windows/WPF project, but the wizard did not complete.

This problem could not be reproduced.

When adding a new datasource, the IDE was closed after selecting a table with Unicode characters in its name.

If a table that contained a field with a Unicode character was linked to a DataGridView, the IDE crashed.

If fully qualified references (project pathname and project name) exceed the Microsoft limit of 260 characters, you might not be able to create the project or reopen it after saving. The recommended workaround is to set a much shorter default location for projects.

To do this, navigate to Tools | Options | Projects & Solutions. For Projects location, either enter a short pathname such as C:\Projects or click Browse and select a high-level folder as the default project location.

ASP.NET

In an ASP.NET project, double clicking a component on the design tab or clicking Event Handler in Properties event would not place the cursor in the correct handler code in the code editor.

You could not retrieve data from a table with Unicode characters in its name in an ASP.NET website.

Database

The dbExpress ADO.NET provider couldn't be used to call methods with parameters of type Single, Currency or TDateTime.

The dbExpress ADO.NET provider couldn't be used to call server methods with TStream parameters or return value.

ExecuteNonQuery didn't work properly with server methods having a TDBXReader type parameter or result.

AdoDbx command parameters were removed when the connection was closed.

An AdoDbx command in/out parameter did not have the correct value after the second execution of a stored procedure. This is related to closing the connection after the first execution.

Known Problems and Issues

Install/Uninstall

If you have Delphi 2007 installed, installing the Delphi Prism Feature Pack overwrites the files dbxconnections.ini and dbxdrivers.ini with the 12.0 version of dbExpress drivers. If you uninstall the Delphi Prism Feature Pack, the uninstaller does not restore a backup of dbxdrivers.ini and dbxconnections.ini with 11.5 driver versions, but just removes all 12.0 drivers.

If Delphi 2009 and C++Builder 2009 are installed on a German system, Delphi Prism can be installed on the system, but uninstalling Delphi 2009 and C++Builder 2009 causes errors. The install of VS Shell removes a pre-requisite installed by Delphi 2009 and C++Builder 2009 (the Microsfot .NET 2.0 German Language Pack). When uninstalling, the Delphi and C++Builder 2009 uninstaller looks for this Language Pack and generates an error. The workaround is to re-install the .NET language pack.

If you install Delphi Prism, then uninstall Delphi and C++Builder 2009, Blackfish service gets shut down. You need to manually restart Blackfish service. The executable for the Blackfish server is BSQLServer.exe.

International

If you create a method with International characters, right-click the editing pane and click Complete Class to create the method implementation, then use Sync editing to change the method name, the resulting method name in the implementation section is incorrect.

The DXCore extensibility framework can be added to Delphi Prism and adds a sync editing feature. This framework is developed by Developer Express Inc. and can be used free of charge for personal use. DXCore can be downloaded here.

IDE

If you drag a typed dataset from the DataSource pane to the Design pane and the grid appears to be blank, the reason is that the BindingSource cannot link to the DataSet table with the DataMember property. There are two workarounds:

• Close and reload the project; the DataMember property will now show the table from the dataset to be linked.

• Alternatively, use the Data | Add data source command to automatically generate the correctly linked BindingSource and DataGridView components.

Platform

If you run a Cocoa application with a NSTextField component, pressing the Control key and any other key simultaneously aborts the application after about 5 seconds. This is a problem in Mono.

ASP.NET

For instance, if you connect a GridView and an SqlDataSource control to a database and enable editing, you might not be able to update data. This problem can occur when the SqlDataSource control has generated an UPDATE statement with the wrong number of parameters. If editing is not working, check the Update SQL statement and parameters. This problem can also occur when the GridView's DataKeyNames property is not set correctly. The GridView.DataKeyNames property should include the name of the primary key.

Database

Optimistic concurrency is not fully supported with Blackfish SQL and InterBase for tables with colums that allow null values. Rows with null values may not be able to be updated or deleted. To turn off optimistic concurrency, use the checkbox in the SQL Datasource Wizard Advanced Options.

If you install CodeGear Delphi and C++Builder 2009 on a German system, then install and uninstall Delphi Prism, you can't connect to Blackfish SQL. You can work around this by adding and starting the Blackfish SQL service bsqlserver.exe.

Allowing only one connection for a local Blackfish database has development ramifications. For instance, if you have the connection open in Server Explorer, then run your application, you get errors if it tries to connect to the database. Close the connection in Server Explorer before running the application.

This restriction is documented in the Blackfish Developers Guide here

"Local connections access the Blackfish SQL database engine in-process. This provides improved performance over a remote driver, but requires that the Blackfish SQL engine be present and running in the same process as the application. Several simultaneous local connections created in the same process can connect to a database. However, only one process can have a database file open at a time. Consequently, while a process has a database file open, it becomes the only process that can connect to that database over a local connection."

After you install Delphi Prism, DataSnap appears in the provider list in Data Explorer for Delphi and C++Builder 2009, even though DataSnap is not supported in Data Explorer. This occurs because there is a DataSnap entry in the dbxdrivers.ini file:

[DataSnap]
DriverUnit=DBXDataSnap
DriverAssemblyLoader=Borland.Data.TDBXClientDriverLoader,Borland.Data.DbxClientDriver,Version=12.0.0.0,Culture=neutral,PublicKeyToken=91d62ebb5b0d1b1b
Port=211

This entry is not needed for Delphi Prism and may be removed, which removes the DataSnap entry in Data Explorer. If you do modify this file, you should make sure you remove only the lines of this entry, since you could cause the product to not function properly otherwise. In particular, do not remove the DataSnap=1 entry elsewhere in dbxdrivers.ini.

This is a permission problem related to network shares accessed from BlackFish service.

You can make it work correctly by following these steps:

1. On the computer where BlackFish service is running, create a new user, say BlackFishUser.
2. On the BlackFish service computer, modify the BlackFish service properties connection tab to use BlackFishUser.
3. On the BlackFish service computer, restart the service so that new user is active.
4. Depending how security is configured on the computer running BlackFish service, you may need to grant permission to files and folders to which the service has access. On a typical Windows XP installation, you don't need to change anything.
5. On the computer where the network share is, create BlackFishUser with the same password as the one you selected above.
6. Open properties of the network share where the database is and add BlackFishUser with full control.
7. On the computer where BlackFish service is running, change the connection properties so that it uses a UNC path (\\MyFileServer\MyShare\whatever...) to point to the JDS file.

If you have a domain, it is much easier. It is sufficient to create BlackFishUser in the domain and use on both the computer running BlackFish service and the computer hosting the JDS file, granting appropriate permissions as indicated above.

When trying to add a datasource that belongs to a firebird DDEX connection with the datasource configuration wizard, the following error occurs: "An error occured while creating the new data source: Could not get type information for 'WindowsApplication.Dataset1'".

This is the result of the .NET assembly not being registered to the registry key at: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\AssemblyFolders.

3rd Party

If you load and build \Samples\Third Party\TeeChart, you get a series of errors, such as: "Error 2 (PE17) Namespace "Steema.TeeChart.Styles" does not exist or has no public types."

Oxygene

Glossaries — Keywords — Types — FAQ — How To