1. Suggestions on Document Tracking solution
If anyone knows of an application that handles what what I'm looking for
then, feel free to mention it... it doesn't necessarily have to
impliment SQL Server.
Basically, my client is looking at tracking e-mail and associated
attachments. The attachments will most probably be the usual office
documents and possibly some TIF files from a fax server solution, which
would e-mail the faxes as they come in to the appropriate mailbox.
The e-mail platform is Outlook 2000/Exchange 5.5.
The solution that I'm thinking of so far involves creating an Outlook
Add-in that would allow the user to sumbit an e-mail to a SQL Server
2000 database in some way.
Once the e-mail is submitted, it will be filed away in a directory
structure of the format date\client ID\e-mail subject ...
for example 200210310730\78901\Your requested quote.msg
The SQL Server (or other database) would then store a link to this
document in order to keep storage space down.
I believe that a solution of this nature would allow it to be more
portable, as anyone (given the permissions required) would be able to
browse the file structure for what the need, should the system go down
or be upgraded.
In the root of the file structure, I believe some sort of text or
XML-based file should track the customer ID and name to assist in this
portability goal.
Any comments, suggestions, and input on this idea would be appreciated.
Is there anything that I'm missing? I'm wondering what would be the
best way to submit the information to the datastore for processing as
well.
----------------------------------------
http://members.tripod.com/kcourville0/
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
2. Microsoft Access Memo Data
3. Trying to avoid a cursor - suggestions needed
4. vnd.ms-excel, PL/SQL cursors and Explorer
5. Request suggestion for concurrent access same table.
6. sp_executesql dynamically built SELECT from SPROC, permissions (roles and SQL Authentication)
7. Index Suggestions
8. how to find the last 100 characters of a huge ntext field in sql 2k
9. Any suggestion for this situation?
10. Suggestions for dictionary-like structure?
11. Slow connections over Named Pipes net-lib ... suggestions
12. database design - suggestions
13. Suggestions on Importing .DBF files into SQLServer