There is still no reason to store the pictures in the db... even with thousands of pictures, you are better off putting the image files on the file system. Think about the things you will have to do to maintain the database - backing it up will become a problem since it will grow very large over time. If something happens and you need to restore, it will take an unnecessary amount of time to restore because it will be so large. You aren't changing the blob that makes up the picture, so it is just going to sit there taking up space in your database, possibly causing the database performance to suffer, etc.

The files could simply be named with the same name as the primary key of the table. And you can partition them by whatever means makes sense - make a new directory each month, or by some product or code for example.

Good Luck!

Wayne

>Hello Wayne !
>Normaly i would agree, but my application communicates with a
>measurement system (roboter)
>I have to store measurement data and a picture of each measured part in a database. So i don't want to store data in a table and thousends of pictures
>in the file system.
>Best regards
>Albert