23 October 2009

The request could not be submitted for background processing.

If you hit the above error message when trying to load the Crystal Report in Visual Studio .NET 2005, then you may try to follow the steps below to resolve the problem:

a). Add the NETWORK SERVICE user into the security of the following folders:

C:\WINDOWS\Microsoft.NET
C:\WINDOWS\Microsoft.NET\Framework
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

b). End the asp_net process in the Task Manager.

c). Recompile your source code.

14 October 2009

Cannot open Oracle 10g OEM in the internet browser?

If you cannot open the Oracle 10g OEM in the internet browser, and Windows is giving you this error:

The OracleDBConsole<SID> service terminated with service-specific error 2 (0x2).

Then, the following details might be able to resolve your problem.

    1. Make sure the PATH, ORACLE_HOME and ORACLE_SID are defined correctly in Control Panel -> System -> Advanced -> Environment Variables -> User variables for Administrator.

    2. Make sure the following folders are exist in D:\oracle\product\10.2.0\db_1\oc4j\j2ee

        OC4J_DBConsole_<COMPUTER_IP>_<SID>
        OC4J_DBConsole_<COMPUTER_NAME>_<SID>

    3. Make sure the following folders are exist in D:\oracle\product\10.2.0\db_1

        <COMPUTER_IP>_<SID>
        <COMPUTER_NAME>_<SID>

    4. You might need to restart your Windows after the above changes.


For more information, please refer to http://forums.oracle.com/forums/thread.jspa?threadID=309223

01 October 2009

DataSource in ListBox and ComboBox

In VB.NET, both ComboBox and ListBox controls allow the software developer to define the DataSource.

However, there might be some errors occur if the way to define the DataSource is not correct.

Sequence to define DataSource and columns name

You are recommended to define the DataSource by the following sequence.

.DisplayMember = mstrDisplayMember
.ValueMember = mstrValueMember
.DataSource = objDS.Tables(0)

Beside that, always make sure that the value for .DisplayMember and .ValueMember are pointing to the correct columns name.


What happen if the sequence is wrong and the ValueMember is pointing to incorrect column name?

Some software developers prefer to put ".DataSource = objDS.Tables(0)" at the first line. If the value of the .ValueMember is incorrect, then VB.NET will prompt you an error message.

Example:

.DataSource = objDS.Tables(0)
.DisplayMember = mstrDisplayMember
.ValueMember = "Incorrect Column Name"

Error message = "Cannot bind to the new value member. Parameter name: value"


What happen if the sequence is correct but DisplayMember and ValueMember are pointing to incorrect columns name?

VB.NET will not prompt you any error message but the result in the controls will be displayed as "System.Data.DataRowView".

Example:

.DisplayMember = mstrDisplayMember
.ValueMember = "Incorrect Column Name"
.DataSource = objDS.Tables(0)

Result = System.Data.DataRowView (if the result returned 3 records, then VB.NET will show you 3 "System.Data.DataRowView")