Click here to Skip to main content
15,886,199 members

Comments by daiwuju (Top 10 by date)

daiwuju 8-May-13 11:17am View    
The demo is coded in VS 2012 WPF, and I rewrite in WinForm by VS 2008 and fix a bug in the demo - the client receiving action is not in an independent thread. I am new to C#, not familiar with the difference between Winform and WPF.
daiwuju 11-Mar-13 4:22am View    
In my application, a server or website provides short-message service(SMS) sending function. When a user login by web brower, he/she submits the mobilephone number and the SMS content, both of which are then input into a SQL Server 2008 database. One program running continously on the server reads the SMS infomation from the database and then sends it to a telecommunication operator's SMS Gateway.
daiwuju 11-Mar-13 4:20am View    
Deleted
In my application, a server orwensite provides short-message service(SMS) sending function. When a user login by web brower, he/she submits the mobilephone number and the SMS content, both of which is then input into a SQL Server 2008 database. One program running continously on the server read the mobilephone number and the SMS content from the database and sends it to a telecommunication operator's SMS Gateway.
daiwuju 6-Mar-13 9:16am View    
It is a stupid mistake. The records, which were not be successfully by another application program until 300 seconds after all the records in SGIP_Submit have been sent to the application program, should be put into another table SGIP_Plan. If the resent choice is made, the records in SGIP_Plan should be inserted back to SGIP_Submit and sent again to the application program. But in the code, the records in the SGIP_Plan is inserted back to SGIP_Submit after 300 second when it was sent from SGIP_Submit for the first time. So for a large number records which causes a long sending time, there would be some unsuccessfully processed records which is inserted back after it has been deleted and before all the records have been sent.
daiwuju 4-Mar-13 20:52pm View    
First, I am very sorry for the use of word "fail". The records left in the table has been reduced greatly to about 0.4% when the record count is more than 1200 if your code runs. I think your last question must be the answer to my problem - there must an other stored procedure that does something to the table. I will check the whole project now.

Thanks!