If MS BizTalk is already a part of you existing solution - you may use it to perform periodic calls to 3rd party web service. Otherwise - creating simple Windows service seems like a reasonable solution to me. Implement a service which will call 3rd party web service with the given period of time. If 3rd party WS reports that remote data were changed - retrieve the new data and store it locally. When user call your (local) web service - just retrieve that data from local storage (previously retrieved by Windows service) and pass that data back to client. Best regards, ----------- Igor Sukhovhttp://sukhov.net -- modified at 1:17 Monday 29th May, 2006

Thx for you help. I try as your said but it's trashy.:sigh:Select of a part datas is base on the Select of whole sheet. I wonder if the OleDb Engineer adjust the type of each excel column when transfer, so when the column looks has more numerical value that it make the numerical type, when the column looks has more string value that it make the string type.:~ === Game is power! ===

Haha..., I got the answer myself. If you write the sentence this.dataColumn.Expression="Col1 * Col2"; after ((System.ComponentModel.ISupportInitialize)(this.dataTable)).EndInit(); then it will work right. But if the code generate by IDE wizzard, it gererate the dataColumn code at the front part, and the sentence '(...).EndInit()' is generate at //Formxx part which must be generated at the end of mothed InitializeComponent(), so, the 'Expression' can not work. As the said, if you want to use 'DataCloumn.Express' property, the good way is written the code yourself after InitializeComponent(). :cool: === Game is power! === -- modified at 1:37 Friday 30th September, 2005

Impliment a containment or Nested class or a Has-a relation.:-D Sreejith Nair [ My Articles ]

You start at different values. When you get to 2.00, you have made a different amount of adds, so the accumulative error is different. That's why the result differs. --- b { font-weight: normal; }

Haha, I found it myself.;) Make this class attributes will be ok. [DesignTimeVisible(true)] [ToolboxItem(true), ToolboxBitmap(typeof(myDialog), "myDialog.bmp")] public class myDialog : System.Windows.Forms.Form :cool::cool::cool: === Game is power! ===

YourForm.OnLoad is an override of Form.OnLoad, which actually raises the event. Using this override would, for example, allow you to prevent the event from being fired, by not calling base.OnLoad. YourForm_Load is an event handler for the Load event and allows you to perfrom some action when the Load event occurs. To follow the previous example, you would not be able to prevent the event from being fired as it already has been. Derek Lakin. The great thing about being a slayer: is kicking ass is comfort food. Buffy Salamander Software Ltd. blog: Digital Thoughts

If you looked at the documentation, you'd see that a Component (or other IComponent implementation) is anything that can be contained with in a container, or more specifically IContainer. The biggest difference? A Control is graphical and has concepts such as location and size, where a Component isn't necessarily graphical. Take the FileSystemWatcher for example. It obviously has no UI associated with it since it just watches files and uses Win32/NT-based APIs. It does, however, have an icon associated with it in design-time. This is because it's a component and can be dragged and dropped onto the design surface. This allows code monkeys to click on it and set properties and event handlers using VS.NET (or any other emerging designer these days). You can, of course, forget about the whole component architecture and type it manually, but this allows the component to be "designed". So, when should you use a control and when should you use a component? If you plan on displaying any UI, you must inherit from control since only controls in the parent's Controls collection are displayed - and it only takes a Control or a child class of it. If you want your "object" to be tied to a designer (even extending the designer with your own ComponentDesigner), you can make it derive from Component. .NET has several examples, such as the FileSystemWatcher, the EventLog, and many, many more. Just go to the overview documentation for the Component class and click on "Derived Classes" toward the top of the page. -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----