Brian
|
| Posted: 03/26/2004, 5:07 AM |
|
hi...
this is kind of stupid question. but
is there anybody knows how to display pictures on grid form?
i have a column on my database table storing file names. and actual pictures are stored in 'Images' file.
thanks
brian
|
|
|
 |
carolcastro
Posts: 24
|
| Posted: 03/26/2004, 5:26 AM |
|
hi brian,
what i did was the folowing:
1. set the field picture you want as a LABEL
2. change the label content to HTML
3. add a BEFORE SHOW
$fotos1->foto->SetValue("<img src=fotos/".$fotos1->foto->GetValue()." alt='".$fotos1->legenda->GetValue()."'>");
it worked for me! :)
see ya!
_________________
Carol Castro |
 |
|
peterr
Posts: 5971
|
| Posted: 03/26/2004, 8:35 AM |
|
You can use the "Image" component/control for this (select "Add Image" in the Toolbox / Forms).
Then specify the database field containing the image in the "Control Source" property.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
brian
|
| Posted: 04/01/2004, 2:39 AM |
|
hi all...
Thanks... it works now. i can see all my product pics.
wow.... i really do appreciate.
|
|
|
|
lesli
|
| Posted: 04/23/2004, 6:28 PM |
|
 i wish that u had pictures with the name lesli to use on the msn messenger
|
|
|
|
Gymsmoke
Posts: 3
|
| Posted: 04/27/2004, 10:00 AM |
|
This may be opening a can of worms, but why not store the images in the datebase?
_________________
Losers always whine about their best...
Winners go home with the prom queen. |
|
|
|
peterr
Posts: 5971
|
| Posted: 04/27/2004, 2:17 PM |
|
Not sure if this really is a can of worms because there are couple solid logical reasons not to do this, all coming down to scalability:
1. You don't want the database busy serving images and transferring large amounts of data, rather than being busy serving what's needed. If the database needs to serve large images then it probably cannot perform other tasks and requsts as efficiently as it should.
2. In scalable environments the database is usually placed on a different server than the Web server. Often several Web servers will actually utilize the same single database. In such environment you don't want to clog the bandwidth between the database and Web servers by transferring images from one server to another. If you ever copied files between 2 computers via network you may even notice that this can be quite slower than copying files on the same computer. Now imagine 1-10 computers (Web servers) retrieving images from poor database server. I would imagine this not only as being slow, but also the internal bandwidth could become somewhat clogged by this.
There probably are some arguments and situations where it's OK to store images in the database, but the above reasons are probably quite solid for not doing so.
Usually each Web server should store a copy of the Website (including images) and then it can serve them immediately and directly to the users' browsers, without stressing the internal network and the database. Some companies use image serevrs specifically for serving images, but I think that they are also stored on disk and are simply retrieved via URLs pointing to such server like imageserver.website.com/abc.jpg
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
