Robby

try this... GroupBox1.Controls.Add(Label1) And then if you get/set the Left of the Label it will be in relation to the Groupbox (As Divil said)

When you say "As New form1()" you are creating a new instance of form1, so it knows nothing about that combo's data. Check out quwiltw's reply near the bottom....http://www.xtremedotnettalk.com/showthread.php?s=&threadid=49478

I can give you an asp calculator, but you won't learn anything that way. :) Here's a link that has lots of samples to get you started. http://samples.gotdotnet.com/quickstart/aspplus/

Did your teacher cover any ASP yet?

It doesn't decrease coding time at all, the couple of sites I did in this fashion were relatively small. Here's the basic structure� The aspx file has one placeholder, and the aspx.vb page has all the event handlers as well as a select case which handles all the classes (which are separate). The entire site can be construed as one application, there are no sales or service. When I started this thread I had not considered any sites as you described "Products", "Customer Support"...etc. You're absolutely right with "it's a good idea to split up large projects into multiple parts"

For me too.

Even if their created at RT, you can itterate the controls and get their values. I'll see if I can test something out.

Me.LayoutMdi(MdiLayout.Cascade) Me.LayoutMdi(MdiLayout.TileHorizontal) Me.LayoutMdi(MdiLayout.TileVertical)

I put together a small sample using textboxes...pagetopagedata.zip

you can use ... Server.Transfer("ReceivingPage.aspx") read more about it here....http://aspnet.4guysfromrolla.com/articles/050802-1.aspx

You can create a new aspx file (maybe call it Popup) and in the calling form put some javascript. Sorry I only know how to do it with JS <SCRIPT> function fnOpenPopup(sPage,sArgs,sFeatures,bMode) { if (bMode == 'Modal') window.showModelessDialog(sPage, sArgs, sFeatures); else window.open(sPage, sArgs, sFeatures); } </SCRIPT> If you want to use this method I'll give you the parameters required.

I created a couple of web-sites using ASP.NET.... In the original design (classic asp) they were about 20 HTML pages and 20 classic ASP pages. Now in .NET I have reduced it to one ASPX file, one Code-behind page and a bunch of classes. IF you have worked with ASP.NET what is your opinion of this approach as compared to creating multiple ASPX pages? Reason for my query? Their are many posts lately that ask how to send data between ASPX pages. As you can see if you have only one page, it is much easier to manage (and distribute)

Are you prompting the user or is th user entering text into a textbox?

You can name it whatever you want... SafeToExit or IsSaved

Are you getting v 2.0 ?

AS a side note.... I noticed you're using lots of member variables, you can eliminate continue by doing this... Function checkSave() as boolean If worksheetModified = True Then Dim responce As MsgBoxResult responce = MsgBox("Do you want to save changes to " & StatusWorksheet.Text & " ?", MsgBoxStyle.YesNoCancel, Me.Text) If responce = MsgBoxResult.Cancel Then return False ElseIf responce = MsgBoxResult.No Then worksheetModified = False return True ElseIf responce = MsgBoxResult.Yes Then mnuSaveAs.PerformClick() worksheetModified = False return True End If End If End Sub Private Sub Form1_Closing(ByVal sender As Object, ByVal e As System.ComponentModel.CancelEventArgs) Handles MyBase.Closing If not checkSave Then e.Cancel = True Else Me.Dispose() End If End Sub

I know that you have lots and lots of fields. In your first post you already said there were nearly 500 fields. Since I can't see your project from 3000 miles away, I'll ask again "what kind of info is in there"? Not to sound rude but In both my posts I'm trying to understand your data.

I understand you have one row per client, what kind of info is in there.

It depends, if there is some data repeated over and over such as Customer information and purchases they made. You would seperate the Customers, Products, Inventory, Sales etc... Can you give us some details on what type of data you have.

I don't think you can do it with server side code.

I'm an idiot for not picking up on it, for sure you can't create the placeHolder at runtime, I assumed that it was done at design time.

Dim PageSetupDialog1 As New PageSetupDialog() PageSetupDialog1.PageSettings = PrintDocument1.DefaultPageSettings PageSetupDialog1.PageSettings.Landscape = True PrintDocument1.DefaultPageSettings = PageSetupDialog1.PageSettings

I recommend .NET 100%, there's VB, C#, ASP, J# and much more. Once you're in you will simply love it. Take the time and learn it right. I would start with a book. http://www.xtremedotnettalk.com/showthread.php?s=&threadid=68986

Check out MS 101 Code Samples ... http://msdn.microsoft.com/vbasic/downloads/samples/default.asp or you can download the one code sample, Automate Office ...http://www.microsoft.com/downloads/details.aspx?FamilyId=BF799731-D4C4-4716-ABD6-74A11BB85C9F&displaylang=en

Printing using which method?