Hi there - I have here a monstrosity of a database!! I developed this for a client to track her art collection. One table, one query, one form, two reports.
All of the fields are text and number, except two which are memo and OLE object (for the photos!)
Each of the photos is about 3.5MB. To insert the images, I have instructed her to right click on the "image" section of the form, choose "insert object", choose "create from file" and then browse to the folder with her pic and insert it.
I left her with this about six months ago. It has now grown to about 250 records
Man, this DB is 2 GIGS!! Needless to say, it performs pretty slow as well...
Any suggestions on how I can temper this little sucker down and make it reasonable in size?
Yea my database for my company originally included small thumbnails. It quickly pushed my database to almost 100MB in about 300 records. I definitely would recommend just having a path and file name text box with which to produce the pictures as you need them. I makes for a much smaller database.
I am about to remake the company database because of several reasons and that just being a small one but definitely one that I want to get away from.
My idea is, you can place JPG pictures in to a folder and place links from database to view them in internet explorer or any other quick viewer (just like irfanview acdsee). Not keeping them in the database!?
I don't know how sounds like. Is it stupitly or good enough??
I witnessed some people using your way. only problem about it you have to click to a button each time to see the picture in explorer. managed file system lets you see the picture while moving through the records, which is sometimes important with most graphic databases for speed browsing.
I'm not too sure what is meant by the file managing system suggested above. I would definitely link to you pictures from the database and display them on a form in an image box. Any events to load the picture shoudl be on code in the on load event and any navigation buttons. I wouldn't let the user navigate through the pictures - you'll end up with them looking at one record and a picture from a different record.
I did the same thing OLE the picture Yeap it got big
What I ending up doing is store the Filename in a Feild
In the Form in the Current Event loaded the Filename in to a image frame
me.pic = LoadPicture(Path&FileName)
hope this help
See clear as mud
the aim is store once, not store multiple times
Remember... Optimize 'til you die!
Progaming environment: Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010 VB based on my own environment: vb6 sp5 ASP based on my own environment: 5.6 VB-NET based on my own environment started 2007 SQL-2005 based on my own environment started 2008 MYLE YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.
My database that holds our parts have them displayed in a 3d manner as much as is possible with a 2D picture. I plan on having a link where the person can click and rotate the 3D object to view all angles from the database.