You should have designed and layed out the application for the minimum resolution you were willing to support. There is no one piece of code that can fix this for you. You have to go back and relayout your controls with the proper and appropriate use of FlowLayout and TableLayout controls, Anchoring, Docking, and other miscellaneous container controls, such as the Panel. It's a bit tricky to do and takes a lot of trial-and-error to figure out how everything works with your setup, but in the end, it makes your form scale to larger resolutions pretty much automatically. A guide to posting questions on CodeProject[^] Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic      2006, 2007, 2008

briogene wrote: SendKeys strCode, True After this can't you send the Ctrl and P keys to execute the print command. hope it help ! AliAmjad(MCP) First make it Run THEN make it Run Fast!

Hi, Please visit the following link to know how you can populate the TreeView from a MS-SQLSERVER database. http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q320755 I hope this helps. Regards, John Adams ComponentOne LLC

I never do Steve Jowett ------------------------- Sometimes a man who deserves to be looked down upon because he is a fool, is only despised only because he is an 'I.T. Consultant'

Try and using INO setup it is a GNU application for creation of setup

Ian Uy wrote: You can use Threads so the form will not lock up That doesn't really solve the root problem. Upcoming FREE developer events: * Glasgow: SQL Server Managed Objects AND Reporting Services ... My website

You really shouldn't do either of these, as they are both pretty bad practice. If you do a select on @@identity, you get the last inserted identity column regardless of scope. So, suppose you insert a record into your table and there is a trigger behind there that inserts into another table with an identity column on it, @@identity returns the id of the trigger insert and not the main table. SELECT max(id) only works if there aren't multiple people posting into your tables at the same time. The simple solution is to use: SELECT @ID = SCOPE_IDENTITY() This returns the identity of the inserted item on the main table, even if you have lots and lots of trigger inserts going on. Deja View - the feeling that you've seen this post before.

You're welcome.