PlausiblyDamp

fileName.WriteLine(System.Environment.NewLine) fileName.WriteLine(strStore) ' write to stream The first of the above lines may be redundant, .WriteLine should write out the data and include an appropriate line terminator (e.g. CRLF)

If you send it back with the same name as the original it should replace the existing one.

You should be able to go to the XML menu and select Create Schema (or similar). It only appears in either the XML view or the Data view for the document (can't remember which though)

Problem is the user (under IE) could go to the view menu, text size and change it. Most other browsers will also allow this. Just out of interest, what are you trying to acheive - there may be an easier solution.

If the font is being displayed in a browser you probably have no way to tell exactly how the browser is choosing to display the text. Every user could have different preferences for size or perhaps they don't even have the font installed.

What is the Message property of the OdbcException?

Where is the string coming from, and would you have any control over the source?

sounds correct, does it work? If so I'd class it as correct ;)

I found http://www.w3schools.com/ quite useful.

http://www.mentalis.org/classlib/class.php?id=15 may be of some use (never used it personally though)

Get a firewall, get some anti-virus ;)

Try this, my code is a bit scrappy admitedly but in a very brief test it seemed to work. I got round the problem by rather than removing from the array I just set the relevant entry to Nothing. Not the best solution but it works for nowtestform.zip

The problem is you are using absoulte numbers for the textboxes but index offsets for the remove at. i.e After adding 3 items the array contains 3 items (0,1,2) If you remove the item from ICD9Code1 then the ArrayList contains 2 items (0,1). If you try to delete ICD9Code2 the aryDiagnosis.RemoveAt(i) is trying to remove item 2 but only 0 & 1 are present - hence the error. You may be better trying to remove them by name rather than the number i. If I get chance I'll have a look at the code later today and see what I can do...

Congratulations!

I know you can set the default document under the IIS Administration tool, does that help?

The older way is less functional, less extensible, slightly slower and incompatible with other .Net languages. If you need to use 3rd party code / dlls that are based around the classes in System.IO then you would have to recode ALL your 'old-style' vb6 file handling code.

It should redirect them to whatever page they originally requested. If they just browsed to the web site and didn't specify a document then IIRC it just redirects to the default document. Where should it have sent them in your case?

Visual C++ programs don't require the .Net Framework (just the C runtimes / MFC runtimes same as always) Managed Visual C++ or C# programs will require the runtime (but this should be included in future versions of windows anyway) Not to sure about the "standalone" program bit - I've never seen .Net being pushed as being able to create apps that run without the framework.

There is no valid cast from a GenericPrinciple (which Threading.Thread.CurrentPrincipal is) and a WindowsPrinciple. They both implement the same interface (IPrinciple) so either could be casted to IPrinciple, neither could be casted to the other. The following should work ' This example assumes that the Principal policy has been set to ' WindowsPrincipal. Dim myPrincipal As IPrincipal ' Gets a reference to the current WindowsPrincipal myPrincipal = DirectCast(Threading.Thread.CurrentPrincipal, _ IPrincipal) Dim myIdentity As IIdentity ' Gets the WindowsIdentity of the current principal myIdentity = DirectCast(myPrincipal.Identity, IIdentity) ' Displays the username of the current user MessageBox.Show(myIdentity.Name)

Is this in managed C++?

The compiler could optimise the call tin Inc() away so performance wouldn't be any different (hopefully). Is there any reason why you don't want to do the x=x +1 thing. How about the shorthand of x+=1 ?

e.Handled = true means you have dealt with the keypress and no further action is required by the control, normally this will result in the key that had been pressed being ignored by the control. e.Handled = false means the control can carry on and process the keystroke.

I think the problem is the Windows Form Designer automatically setting the text to the name of the control on creation. Even though your sub new is setting the text property to "". If you look in the designer generated code you will see some asignment to the .Text The DefaultAttribute may help... http://ms-help://MS.VSCC.2003/MS.MSDNQTR.2003FEB.1033/cpref/html/frlrfsystemcomponentmodeldefaultvalueattributeclasstopic.htm

You can't set a reference to an .EXE in .Net only Dlls. If you create a classlibrary you add forms to it in the same way you would to an .EXE project.

You will also need to set a reference to the DLL (Project menu->references)