depository database

crescent-centre

Registered User.
Local time
Today, 00:36
Joined
Feb 28, 2003
Messages
30
I need to have a database that users can add actual files into, not just a link. These files could be Autocad drawings (1MB - 2MB) , Word documents, PDF or Tiff files. Any suggestions.
 
yeah, don't use access for this.. use SQL server or some other "larger"/ enterprise type database. Even MySQL would be better than access for this.
 
Kodo said:
yeah, don't use access for this.. use SQL server or some other "larger"/ enterprise type database. Even MySQL would be better than access for this.

Are you saying that Access doesn't work or that MySQL works better. I know nothing about SQL.
 
No, You CAN use Access, but it is really not the best database to use to store a repository of large files like that. It will choke evetually and you'll end up moving to larger DBMS.

MS-SQL server is a good choice for a backend. You can use Access as your front end and use MS-SQL Server as your backed to store your files. It can handle what you want to do much better. MySQL is a free alternative but is not as robust as MS-SQL server.
 
Kodo said:
No, You CAN use Access, but it is really not the best database to use to store a repository of large files like that. It will choke evetually and you'll end up moving to larger DBMS.

MS-SQL server is a good choice for a backend. You can use Access as your front end and use MS-SQL Server as your backed to store your files. It can handle what you want to do much better. MySQL is a free alternative but is not as robust as MS-SQL server.
Ok, understand your point, however how do I store actual files into the database? I'm planning on trying Access to start with to prove the concept.
 
This is a concept I wouldn't try to prove. Remember that you have a size limit in Access that relates to its method of addressing. If you are correct that you will have 1-2 megabyte files, your database will be full when you have loaded between 1000 and 2000 files. Full as in "no more room" in its internal address space. No matter HOW big your hard drive happens to be.

The way to do this is to POINT to the files. Store a file specification string and use some VBA code to open or otherwise manipulate the files.

You NEVER EVER want to store files in a database. It is not a file system. It is a record storage system. Use file systems to store files. Otherwise you are just re-inventing wheels that don't need re-invention.

Sorry if this sounds abrupt and dismissive, but I'm hoping to save you time, effort, and many headaches down the road.
 
I agree with Doc.. however, the one thing I like about using a database to store files is referencing them per an account is much easier to code for.
 

Users who are viewing this thread

Back
Top Bottom