private const int WS_CHILD = 0x40000000; private const int WS_CLIPCHILDREN = 0x2000000; private const int WS_MINIMIZEBOX = 0x20000; private const int WS_MAXIMIZEBOX = 0x10000; private const int WS_SYSMENU = 0x80000; private const int CS_DBLCLKS = 0x8; protected override CreateParams CreateParams { get { CreateParams cp = base.CreateParams; cp.Style = WS_CLIPCHILDREN | WS_MINIMIZEBOX | WS_SYSMENU; cp.ClassStyle = CS_DBLCLKS; return cp; } } _______ JeniuS - the file Organizer

thank you Heath and Dave for your hints. I followed Dave's one (much simpler) and it works. here is the code that does the job: [DllImport("Kernel32.dll")] private static extern uint SetThreadExecutionState ( uint esFlags ); private const uint ES_SYSTEM_REQUIRED = 0x00000001; private const uint ES_DISPLAY_REQUIRED = 0x00000002; private const uint ES_CONTINUOUS = 0x80000000; private void disablePoweroff() { SetThreadExecutionState(ES_SYSTEM_REQUIRED | ES_DISPLAY_REQUIRED | ES_CONTINUOUS); } private void enablePoweroff() { SetThreadExecutionState(ES_SYSTEM_REQUIRED | ES_DISPLAY_REQUIRED); } thank you again, bye ________ http://www.jockersoft.altervista.org

Don't use a DataSet. It outputs XML in specific ways - namely as elements. Instead, see the classes in the System.Xml namespace. You could enumerate the tables and columns in your DataSet (or use an XmlDataDocument) and then write them out to a file using an XmlTextWriter, which allows you to write attributes, elements, comments, and even processing instructions however you want. Lots of samples are included in the class documentation for the System.Xml namespace. One other option is to save this to a file or a MemoryStream and then load it into an XmlDocument or some other class. You could then use a XslTransform to transform the elements into attributes. Microsoft MVP, Visual C# My Articles

You simply have to review the documentation on MSDN. Get to know what classes there are. It's not like you have to memorize the whole library, just become familiar with what certain namespaces cover (ex, obviously System.IO is for input/output, which includes files and other streams) and you can always lookup stuff when you need to. API documentation is not to teach you how to do things - that's your job and what development is all about. Besides, nothing says you have to use one class over another, or that you couldn't even write your own. Some classes may be better than others for particular uses, but your understanding of those classes and your imagination in how that functionality can be derived is what dictates which classes you should use. -----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-----