saving received emails into ms sql server 2000

Hi, narmi2.

This is possible, although there may be a few hoops to jump through to make it work.  A couple of questions first to get a clearer picture of what you're looking for.

1.  Do you want to save the message as an object or will the SQL table the message goes in have fields that mirror a message's properties?

2.  Is your mail on an Exchange server?  If yes, do you expect this process to work from the Exchange server or only from Outlook when it is open and running?

Hi BlueDevilFan

1. I would like to save the mail properties into proper table fields, i.e. the person who sent the email should go into a column called "from", the subject should go into the "subject" column and so on.

2. Yes we have exchange server.  Preferably, I would like it to work from exchange server, so I don't have to go to every employees PC to modify their outlook.

Thanks for the reply.

Hello again.  I'm going to address the issues in reverse order

2.  Not easily done.  Doing this at the server requires writing something called an Exchange event-sink.  Event-sink are to Exchange as macros are to Outlook.  They are blocks of code that are triggered when certain events occur, like mail arriving in a mailbox.  However, they are more complicated to write and any errors in an event-sink could bring the Exchange server down entirely.  They are definitely not for the inexperienced or faint of heart.  I am not prepared to write an event-sink.  I can describe in general terms what it would need to do, but that's it.

1.  Easily done.  There is one hitch though.  Assuming that you do this at the Outlook client instead of at the Exchange server, then accessing any message property that can contain an email address is going to trigger Outlook's built-in security measures.  The result will be a pop-up dialog-box warning that an application is accessing your mailbox and asking you for permission to allow it to continue.  That would pretty much kill any sort of automatic process.  Outlook security cannot be turned off, but there are workarounds.  You can use a third-party tool like Click-Yes to click the Yes button for you each time the warnign appears, or use another third-party tool called Outlook Redemption to safely avoid Outlook security.  Another alternative is to write this as a COM add-in.  The result would be a DLL that you can distribute to your clients.  COM add-ins have different security constraints than macros do and are not subject to the warning message.  

Getting the message properties into an SQL table is easy.  It simply requires creating a connection to the SQL server using ADO and executing an insert statement.  The real issue is where the code will run at (client versus server) and security issues.  I don't have an SQL server at hand, but I can post a sample macro demonstarting the proof of concept using an Access database.

Thanks,

Looks like I will have to stick to the first approach.  How exactly do I do that, I do not know how or where to write my sql insert statement in outlook to get it to insert the email info into my table.  Do I have to use VBA?

If i am to use VBA, which trigger even do i need to detect that a new email has arrived?

Yes, you'll use VBA.  I'll post some sample code (it'll be later today/tonight) showing how to do this using VBA and ADO.  My example will use Access, you'll just need to change the connection string to use SQL Server.

thanks

the sample code will be very useful