- In crystal report viewer, link the report source to crystal report source.
- finished

so now you can edit the sql query in sql data source in code behind, like for example for the select query in sqldatasource1:
Sqldatasource1.SelectCommand = “[your sql query]“

This happened because multi lines readed as a long line, so the above example is read as : select a,round(b,2 –comment ) from table,

2. adding “order by” in “IN” clause in “where”.

3. adding user defined function inside sql statement.
ex. select myfunction(a) from table

4. adding “order by” next to “union” two select clause.

5. forget to add comma in between parameter/entries in “decode” statement.

some other things can trigger this error also, but this is because of the bug in oracle version, like in oracle 7 when use use “case” inside in sql query.
or in oracle 10 before 10.2.0.3 using full/left outer join in link with Bug 4433936.
or using quote inside quote, like ‘xxxx’xxxx’xxxx’ as a single string will throw error also, to correct this use the quote inside twice, like: ‘xxxx”xxxx”xxxx’

- makes windows 7/2008 dvd ready in the drive tray.

- format the flashdisk.

- using command line, enter the windows dvd drive then type in its root: boot\bootsect.exe /NT60 [flashdisk drive]

then type, still in its root:
xcopy *.* /s /e /f [flashdisk drive]
(or using windows explorer copy all files from the windows dvd, including the hidden one to the root of usb flashdisk.)

*Note, in order for you to be able to use bootsect.exe make sure your system is the same bit with the windows dvd, e.g. your windows is xp 32 bit, then the windows 7 dvd is the x86 version not the 64 bit version.
but there is a run around for that, you can use the bootsect.exe from 32 bit version but copying the 64 bit version and vice versa.

and there are other software that can make bootable usb, personally since those steps above won’t work for xp, so I use Novicorp WinToFlash – currently in beta – to create the usb windows installation.
btw. you still cannot create x64 usb windows 7 installation disk on 32bit system (xp or vista/7/2008). so the manual steps above is better.

Now this is the problem, based on the tutorial it should generate “connected” status, even though i’ve tried using the proper form of “connect sys/manager as sysdba” it still generating TNS error.
First since it was TNS error i look for multiple TNSNames.ora but there were no duplicity, only one found in each database and in developer folder.
So after failed asking to master google, i tried to contact the other master in the flesh. There he scribe me to do these steps: – open command prompt.
- type “svrmgrl” so the prompt changed from “c:\>” to “svrmgrl” – there type “connect sys/manager as sysdba”
(here i finally able to connect)
- then type “shutdown”, it will generate:
(ORA-01109: database not open)
(database dismounted)
(ORACLE instance shutdown)
- then you type “startup”, you’ll see the status of the database: (ORACLE instance started.)
(Total System Global Area xxxxx byte)
(Fixed Size xxxxx byte)
(Variable Size xxxxx byte)
(Database Buffers xxxxx byte)
(Redo Buffers xxxxx byte)
(Database Mounted.)

if nothing show up after that, just the ‘svrmgrl>’, then congratulation, your database is ready for transaction!

but now if after that, you found instead some ora error like: ORA-01113: file xx needs media recovery
and/or ORA-01110: data file xx: ‘[DBF file parth]‘
then you should repair the file, for i because too lazy i just drop user–> create user–>import the data…

anyway, back to the tittle, it seems that every time i make it over 127 columns when i save it, the visual studio crashed (actually i can save it at 127 columns, but when i add 13 more bound fields, it crashed). the strange thing is that it is ok if you use automatic generating field option, but not ok if you manually add the field yourself…

but don’t worry there is a work around to that, but this is with a consequence,
you cannot again enter the “design” mode of your aspx page once you add the bound field columns manually through “source” mode because it will crash your visual studio and be mindful, that the visual studio will use 100% source of one of your processor (the visual studio standard version i use, seems only to use one processor, even though you configure the affiliation to all your processors)

we then open the browser and entering the IP Address, and you know what? It turned out to be a DLink Print server.
And that leaves us with more mystery, since we already put the static address to the device through print server application (PS-Admin). Anyway, we continue to see the detailed network configuration on the device, and it turned out (again) that this print server can have two IP Address, one is for its UPnP (?Universal Plug n Play?) connection.
so we disable the UPnP function and save the configuration…

++++problem solved+++

The following conditions are necessary for the correct functioning of 48-bit LBA ATAPI support:
A computer with a 48-bit LBA-compatible Basic Input/Output System (BIOS) installed.
A computer with a hard disk that has a capacity of greater than 137 gigabytes (GB).

You must enable the support in the Windows registry by adding or changing the EnableBigLba registry value to 1 in the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Parameters

To enable 48-bit LBA large-disk support in the registry:

• Start Registry Editor (Regedt32.exe).
• Locate and then click the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atapi\Parameters
• On the Edit menu, click Add Value, and then add the following registry value: Value name: EnableBigLba
• Data type: REG_DWORD
• Value data: 0×1
• Quit Registry Editor.

So then I checked the server performance using performance monitor, there I saw disk queue waiting time had reached the roof. so to get the detail I added another parameter on individual physical drive, then I saw that the SATA drive had very low performance. So I installed HDD diagnostic utility HDD sentinel since it is freeware. There I saw that the read/write was so slow, only in 10′s kilo bytes.
After days tweaking from bios, to the system and hadn’t been able to made a differences, I took off the casing side and looked inside and something hit my head, why should I use the SAS cable? So I took it off and use the regular SATA cable and restarted the server, reimporting my database and it even faster than the regular 30 minutes I took using SAS drive…
dunno why, SAS should be faster than SATA it is 15000 rpm twice the SATA 7500 rpm.
Anyway, since it is better now I refuse to inquiry further, hehehe… let sleeping dog lie.

well we just having visited by a technician where my company bough ICA UPS. we got nice info on how to configuring the UPS.
you know if you open the ICA UPS, you’ll see a board right? in that board you’ll see number next to the blue thing that you can turn left or right (like a screw).
now you find the number 201, 501 and 401.
the number 201 is to set the output of your UPS, to set it right you need a multitester or av tester. just using a screw driver you turn it to the right to increase and to the left to decrease, the recommendation is 220, since it is the factory default for any electronic appliance today.
now the number 501 is to set the input, if the electricity of your home is not within a good range (like below 160v or above 240v) then you calibrate it to 224v.
now the 401 is to set when you have problem when sudden surge on/off from the AC electricity of your home or the AC of your home is too low that makes the ICA cannot take any power input from your home AC. the tester wont be showing you the change when you calibrate the 401. only when you turn it too to the left the ICA UPS will stop accepting AC power from outside. (it will start to beep like when the electricity is off).