To design programme (what to use )

My friend, what he needs is a program to organize all the junk he gets daily, lol, so what you need to do is an item catalog, as simple as that. You dont need to store the actual document on the database. Simply make tables to keep track of WHERE ITCAN BE FOUND. then make an interface that allows him to enter new documents, and select the location trhough a dialog box. You copy or move the file to a convenient location designated by the parameters that user has selected to organize it. For example, lets say he receives a word document, and this document belongs to section 3, then you let him select the file with a dialog box, and then copy or move the file to a folder called:
C:\Program files\YOURPROGRAM\Catalog\Section3\thefile.doc
Then you record its location on the database. Next time the user requests this file, you launch it with a shell command.

Simple as simple can be!
he he

If you have any questions, or require assistance, send me an e-mail. I can help you design the application too (for a very reasonable fee, he he :)

Good Luck!

Thanks for your answer.

your fee proposal is good if i need some more technical i sure contact you.

i started with VB,SQL
i use VB Antomation Ole to open the word.
after opening the document if user choose save or saveas then event raise andfilepath is trap and store it to the SQl

now i want to trap the filepath from word/image(save/orsaveas box)

can any one tell me this

AThakker

As mentioned, you only need to store the locations of the files, not the actual contents of the files. In addition, you should store in each record data about each file (ex: title, date created, last modified, summary or keywords, created by). A database application is certainly the answer.

I would suggest using Access, rather than the VB/SQL you mention. Access will let you call Word, etc., to display documents and will enable you to rapidly develop an application and database. Unless you are talking a very large database (say 500,00+ records), and/or many users (over 20), and/or the need for remote access over less-than-speedy network connections, Access 97/2000/2002 will provide an effective solution and be much easier to use fordevelopment.

If you must use SQL Server (version 7/2000/2002) and have at least Access 2000 available, you can develop an Access "Project", which connects directly to SQL Server (and doesn't use the Jet engine at all). (You could also initially develop using Access and the Access Jet database engine, and if the database gets too large for decent response times, move over to using a SQL back end with the Access front end or more to Access Project.) If you are interested in using Access Project (which is included in Access 2000 and later), I would strongly suggest purchasing the book "Microsoft Access Project with Microsoft SQL Server", written by Ralf Albrecht and Natascha Nicol and available from Microsoft Press.

This question was auto closed due to inactivity