I believe you need to do it in conjunction with an Exchange server. It involves creating a security settings template in a public folder. Here's a link to two Microsoft articles on the subject. The first one explains what needs to be done to set up the template, and the second one explains what each setting on the template does. http://office.microsoft.com/en-us/assistance/HA011402931033.aspx http://office.microsoft.com/en-us/assistance/HA011402951033.aspx The setting you configure is on the "Programmatic Settings" tab. It's called "When sending items via Simple MAPI: Automatically approve". There is also a "Trusted Code" tab on the template. On that tab you can specify COM addins which can bypass the security blocks in Outlook. What settings you use depends entirely on the type of application you're trying to send e-mail from. Also, I believe there is a registry value on each workstation which tells Outlook to get its security settings from the public folder form. It was: [HKEY_CURRENT_USER\Software\Policies\Microsoft\Security] "CheckAdminSettings"=dword:00000001 Hope that helps. Scott...

If you want to define a different hyperlink per row you can use the InitializeRow event. Here is an example from the Infragistics website: private void UltraWebGrid1_InitializeRow(object sender, Infragistics.WebUI.UltraWebGrid.RowEventArgs e) { e.Row.Cells[0].Value = "<a href='http://www.infragistics.com/go.aspx?id=" + e.Row.Cells[0].Value.toString() + "' >" + e.Row.Cells[0].Value.toString() + ""; } Check out here for more info. Hope that helps! -- modified at 13:45 Wednesday 12th April, 2006

Yep - backups worked well with Postgre.

We used PGAdmin as our admin tool, and to run our DB scripts. We used DB scripts for doing everything (table changes, function creation, triggers, etc). As for the 32 parameter limit - that is specifically for DB fuctions (AKA stored procs). This was an issue for us as we did everything with functions (inserts, updates, and deletes) and any table that had more than 32 columns caused us issues. To get around it we had to use arrays as parameters and fill those in code before passing into the DB functions - not pleasant but it worked - and the way we architected everything it was hidden from most of the developers in our data layer. I don't recall any major bugs that we found - mostly little things mostly related to syntax in our functions and special characters. Nothing a google search couldn't fix for us.

I have used PostGRESQL quite a bit - I worked as a technical architect on a large web-based application (developed in Java) a couple of years ago and it used PostGRESQL exclusively in it's back end. Coming from a primarily SQL Server background, I was quite satisfied with PostGRESQL's performance. There were a few gotchas that caught us along the way (the 32 parameter limit for functions was one that I remember fondly). Any specific questions about PostGRES that you are interested in?