Nah, we all always have enough coffee, even if it means going in to the office to get it.

You got my vote. Good luck! :) WE ARE DYSLEXIC OF BORG. Refutance is systile. Your a$$ will be laminated.

I am sure a committee decided which names to use. I am not confused by these two names... This is not a std specific problem. We have the same problem in almost all libraries: empty, clear, remove, delete... hard choice. Luckily we cannot use void... we can use Void, _void, etc... :)

It would be worth discussing it with your host; your host may very well provide some kind of scheduled task service themselves. There are approaches to use though if your requirement has to be within the context of ASP.NET code. You could start a new thread in the Application.Start event to poll for your emails. This article shows an example of that approach: http://www.angrycoder.com/article.aspx?cid=5&y=2003&m=4&d=11[^]. As the article author points out, there are some pitfalls to this approach, but you can decide if it will work for your setup.

Thanks Warren - I've needed something like this more then a few times. Site looks great too. - Dy

ThatsAlok wrote: oops you giving invitation to spam :~ why do you say so ? :(( TOXCCT >>> GEII power [VisualCalc 3.0  updated ][Flags Beginner's Guide  new! ]

Example #2 is pretty well done in Orcas - when you make one of the "common" mistakes a little UI thing appears and one of the options is to fix the error. Works for things like missed imports etc. '--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd

Robert, Yes! That's exactly what I was looking for, I just didn't know the syntax. Thanks very much! :) Warren

I found this submitted as bug ID: FDBK17799 at Microsoft. The final (and not so helpful comment) was: ============================ Resolved as Won't Fix by Microsoft on 2005-07-27 at 12:31:15 Thank you for reporting this issue. We've been reproduced the bug for Resource IDs >= 32768. Unless you are using that many IDs we suggest to use Resource IDs < 32768. Sorry for the inconvinience. =========================== (which conflicts with the ID-range advice from: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/\_mfcnotes\_tn020.asp but maybe for the time being, I will change my IDs to this lower range, and take my chances down there :wtf: :wtf: :wtf: Warren

You might try looking at Telligent's community server package. there are various licences available including free to non profits:-D http://communityserver.org/ It's used by the guys at #develop and it seems to work very well. End of Line.

Hi Damir. Damir Valiulin wrote: Sorry to bring up this 6 month old post I don't mind discussing a 6 month old post, mainly because I can't say I really came to a definitive conclusion, and I feel the question remains to be answered. Damir Valiulin wrote: I was working on certain ...Prop application...My task was to "fix it up" and I had two month (with lots of overtime) to do it. I'd have to say I'm one of the few people who can really appreciate that...and it must have sucked. I hope you at least got a good bonus for your suffering :-D Damir Valiulin wrote: I ended up almost rewriting the whole thing. That seems to be a recurring theme. Unfortunately (and this seems to be common to almost all programmers) once someone sees an application that has 80% of the required features, it's very hard to convince them that the project should be started from scratch because the code is a steaming pile of .... X| If you want to build commercial-quality software that will last for many versions/years, it simply cannot be built from a foundation that was written by a student. Period. :sigh: 1) Yeah, absolute pixels are right out of the 1980's !?! XAML should fix all of that - assuming you don"t have to ship anything before 2009 ;P 5) I can't say I'm totally up on the subject, but I don't see how decent code protection (e.g. hardlocking) could ever be done in a byte-code system like .NET. From what I've seen, even obfuscated code is fairly readable when "disassembled". I don't think Microsoft is overly concerned about this, so I'm not sure if it will be solved any time soon. 6) I absolutely and totally agree with you on exceptions. They look great on a computer science chalkboard, but aside from file I/O, I would say exceptions are highly overrated for writing practical code. I think the main reason they're so popular these days is that it's great for framework authors (they just say "the caller will deal with it" and they're done), while sticking people like us with the hassle of catching all of their problems. And (finally), for the topic at hand... I considered C#/Winforms/etc quite thoroughly (I bought and read through a good number of books, and tried tons of sample code) and my opinion is: i) I found C# very elegant compared to C++ (e.g. properties, events), with the exception of not having destructors (whi