Board index Database Programming

Binding an Image control to an Image field in SQL Server

Binding an Image control to an Image field in SQL Server

Post by Barry Belfor » Thu, 14 Jan 1999 04:00:00



I'm having a problem binding to a SQL Server image field using the
dataenvironment.  I've got the field type set to picture, the data memeber
set to the correct table.  I get a problem when I open the form.  It says
that it is unable tobind to the field.  It's not a problem with the data
since I've tried it with and without data in the field.  I am able to link
to the table in access and I'm able to view the in access.

I've also tried using a PictureBox and an OLE field and get the same
problem.

Any suggestions would be appreciated.

Barry

 
 
 
Top

Binding an Image control to an Image field in SQL Server

Post by <CNS> » Fri, 15 Jan 1999 04:00:00


This is a real problem with VB6 .. I had the same problem .. You may see
previous messages posted under the heading "ADO and Pictures" in this
newsgroup
Regards

>I'm having a problem binding to a SQL Server image field using the
>dataenvironment.  I've got the field type set to picture, the data memeber
>set to the correct table.  I get a problem when I open the form.  It says
>that it is unable tobind to the field.  It's not a problem with the data
>since I've tried it with and without data in the field.  I am able to link
>to the table in access and I'm able to view the in access.

>I've also tried using a PictureBox and an OLE field and get the same
>problem.

>Any suggestions would be appreciated.

>Barry


 
 
 
Top

1. images in image fields and field bloat

OK, I'm doing some research on storing image files. I've
read that most programmers prefer to store links to the
image on the server, mostly because of the bloat
associated with storing them in general fields. I've done
some tests using VFP 7 and SQL Server 2000 with image data
type for field. I've watched my database file go from 1Mb
to 6MB with the first 30Kb file added, and 3MB for each
30Kb file after that. This seems excessive!!! 150%-200% I
could live with like I've read from some people, but this
(10,000%)? I only added 3 records and maybe it falls off
after a certain point, but is there some configuration
that I'm missing here?

I'm adding the record to an updateable cursor and then
using APPEND GENERAL XXXX FROM GETPICT().

I would like to store the images in general fields, just
because then I don't have to worry about extraneous image
files sitting around on the server when they retake the
image, but I don't think I can live with that kind of
storage bloat.

Any ideas or is this normal?

2. Datagrid Firstrow

3. JPG Image in Seagate Crystal Report from SQl Image Field

4. Enterprise Manager Access over the Web

5. How to load an image to an image field of a SQL Table

6. VISUAL BASIC CONSULTANTS NEEDED IN FLORIDA

7. Putting Images in to a Field with the Image type in SQL 2000 Ent

8. Unable to delete NorthWind MetaData

9. Loading Images from Access into Image Control

10. How to display image from mbd database in an Image Control

11. Image Controls - Image Basic

12. Image Datatype - binding datasource to a controls picture property

13. Data Bound Picture or Image Control in JPEG format


All times are UTC
Board index