Mark Nischalke wrote: You could make it a HTA. Write a HTML page and change the extention to hta. Perfect... that method had slipped my mind. -AC MCDBA http://www.aconnell.com

Paul Watson wrote: no, not those kind of fruit cakes all you sickos Hahaha, nice touch. Now I just need to find my info on each of the parsers (which one has the flaky XSL parser). -AC

Andrew Connell wrote: Would this be something of interest to others? Hell yes! :-D We can either just carry on moaning about IIS security or we can learn how to lock it down as is needed. A systematic article on locking down IIS and SQL would be very useful, especially if it comes from real world experience and not just theoretical pondering :) Paul Watson Bluegrass Cape Town, South Africa Ray Cassick wrote: Well I am not female, not gay and I am not Paul Watson

Have WinXP Pro on my laptop and found no problems. I use VS6 there though. My desktop has Win2k Pro with WS.NET installed Also watching DVDs on laptop everytime, works just fine, even enough battery to finish the movie :) Philip Patrick Web-site: www.stpworks.com "Two beer or not two beer?" Shakesbeer

I run XP on my desktop, Win2k Server on my laptop, and Linux 2.5.15 on another desktop. I've used XP Server on the same laptop with no problems, but needed a Win2k Server environment, and that's why my desktop now runs XP. As a dev. platform, XP is fine, I just kill all the themes so it looks almost identical to Win2k. (There are plenty of sites out there that give you tips on speeding up any Windows OS.) As far as power management: never had a problem. Works like a charm.:wtf: -- ian http://www.ian-space.com/

I use the following: Alpha - Release to other developers, usually with full source and run in "debug" mode. Beta - Release to other developers and a select few who are possible stake-holders in the release (i.e. people who need the new functionality asap, bugs and all) for testing and quasi-production. Note, the build is likely still debug, but the application stands on its own. Release Candidate - When the product has all* bugs worked out, and an installation program has been built for the release, I will distribute the product to those users within my personal knowledge who really want it. The application is "release" build now, with optimizations and no debug info. Final Release - That's it. After any last-minuite updates, a new Install is built, and release is available for anyone who wants it. *as far as we can tell... - Nitron "Those that say a task is impossible shouldn't interrupt the ones who are doing it." - Chinese Proverb

I got a reply to my similar posting on GotDotNet[^] by an MS guy. He has a work around that seems VERY easy and not too hacky. :-D What he said he did is to use a 'fake' hyperlink and used the BeforeNavigate2 event to find out what the hyperlink URL is. I'm going to try this as it seems like a good solution for me. My URL will be a flag like <a href="OpenCollection.1"> and I'll just have a switch statement inside my BeforeNavigate2 event handler method. -AC

does InventoryRow directly inherit from DataRow? if not there might be problems casting it

Yikes!:eek: That's something I definatley don't want to get into. I'd much rather deal with the native DataRow objects than manually add each item into the typed object. That seems like a TON of overhead. If I find anything I'll be sure to post it. In the meantime, I'm investigating MAPPING and merging the two different types. If I can do that in my data access layer/components, and just continue on with the application development, then I'm fine with that. Andrew Connell, MCDBA IM on MSN andrew@aconnell.com

It is done by using the MS HTML engine together with the HTML DOM engine in IE. The text for the HTML is stored in strings in the application, and they are outputed to the IE control via the DOM calls (document.Write("bla") in javascript) Events get raised up into the application, so clicks can be processed by the EXE. This is all still a bit of a hack. I can't wait for when they get it really right, with a form designer built from the ground up with all the features of IE for rendering.

Override the WndProc procedure and handle the Windows Message WM_LBUTTONDOWN: class TreeNodeExID : TreeNode { ... public const int WM_LBUTTONDOWN = 0x0201; protected override void WndProc(ref Message m) { if(m.Msg == WM_LBUTTONDOWN) { //DO WORK HERE } base.WndProc(ref m); } }

Oops, got me there. Even in the .NET framework they can't keep these properties too consistent ;)

I must admit this confused the hell out of me - I wanted to have several web forms up at the same time and it took a while before I worked it out. now just got to work out how to talk between them Holy Handgrenade of Antioch instructions

It is very easy. Just look under the appropriate directory open the appropriate file and modify it. For example if you want to modify the default Class generated by C# in it under VC#/CSharpNewItems directory. ..this is a VB Programmers' world and we all are just visitors - Someone in a MSJ article

Since this would cost you a (probably rather hefty) bunch of money, perhaps you should try e.g. CVS first?

www.starbase.com

Or do this: MainContainer mc=(MainContainer)(this.theTopMenu.ParentForm) Then: mc.SomeMethod() mc.AnotherMethod() Jerzy

Got it... Form2 frmForm2 = new Form2(); frmForm2.TopLevel = false; //<<< KEY CODE frmForm2.Parent = this; //<<< KEY CODE //position 200px down from top because top 200px are my app header System.Drawing.Point thePoint = new System.Drawing.Point(0, this.ClientRectangle.Y+200); frmForm2.Location = thePoint; //size child form to fill up 100% of the parent form EXCEPT for the upper [form width]x200 System.Drawing.Size theSize = new System.Drawing.Size(this.ClientRectangle.Width, this.ClientRectangle.Height-200); frmForm2.Size = theSize; frmForm2.Show(); Andrew Connell IM on MSN andrew@aconnell.com

i am also asking for that! :confused: :)