In most cases, the error made by the developer when changing a lot of data on a table is to forget the (re)generation of the index. Such an error will degrade the performance of all queries made during the day with indexes generated automatically during the night.

Using the CSRCustomMenu class gives the opportunity for the developer to control at least the behaviour of the items and the type of the internal variable used for storing the information. The subject of this entry is to detail the virtual methods which have to be overloaded in order to control the type of the variable.

Imagine that the instrument dialog was overloaded by toolkit, and that the sicovam is required to make some SQL query when opening the insturment dialog. If there is no test on the fact that the instrument is displayed in audit mode, this will certainly fail since the sicovam given by the CSRInstrument will correspond to the "new" sicovam and not the one used in current mode.

In most cases, and on versions of Sophis Risque before the 6.0, it is not possible to access to the native fields using the toolkit Sopshis method GetElementByRelativeId, beacause such fields are not natively a CSRElement.

The goal of this post is to show how to use the Low Level Toolkit, in order to update the display, and the internal structure on a specific case (Folio creation/modification).

Familiar to click simply on the menu item on C# .Net 2.0, during the design, in order to implement the corresponding method, I was a few confused by the way to implement it on .Net 4.0, by using the WPF.

This post will give the solution on how to declare WPF Menuitems in order to be able to use them in the callback.

The obective of this post is to describe the properties to set on the different WPF controls in order to have:

- a menu which has the same width as the application (and not restricted to a default width)

- having a chart control which resizes inside the client area, without overlapping the menu control

Since it tooks me a few minutes to retrieve the right proeprties to set in order to have a main menu, this article describes exactly what to do to have:

- no margin between the menu and the title bar

- have the main toolbar menu that is resized with the main window

Needed and usefull for instance on unitary tests when creating new instruments in order to get new references and not to violate primary keys

Currently making extractions of messages that should contain some keywords, sometimes the number of occurrences retrieved is too big. The only way is either to redefine the keywords (HI% could become HIGH for instance) or to count the number of words between two keywords.

This is possible with the Platform toolset available on the General tab of the project configuration. By default, you can target either VS2010 (platform target v10) or VS2008 (platform target v9).

The platform toolset selection is available as follow: