[AccessD] A really silly and dumb - maybe even ridiculous -access question

Hi Charlotte,
Thanks for responding. Yes there is a reason it is stored. It is the only
image I store in any of my database apps. The rest I use from files as you
suggested. This is probably why I don't have a clue as to what to do here.

I could spend a couple of hours reading up on it but I thought somebody here
would have some experience in doing this and be able to point me in the
right direction :o)

JB

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte
> Foust
> Sent: Monday, October 27, 2003 3:41 PM
> To: Access Developers discussion and problem solving
> Subject: RE: [AccessD] A really silly and dumb - maybe even ridiculous
> -access question
>
>
> Is there a reason you have it stored as an OLE object in the table
> instead of just storing the name of the file?  In the latter case, you
> could use an image control and set its picture property to the path and
> filename of the object.
>
> Charlotte Foust
>
> -----Original Message-----
> From: John Bartow [mailto:john at winhaven.net]
> Sent: Monday, October 27, 2003 1:38 PM
> To: AccessD
> Subject: [AccessD] A really silly and dumb - maybe even ridiculous -
> access question
>
>
> How would I go about reading an OLE Object field type from a table and
> present it for display on an unbound  form?
>
> John B.
>
> It looks like "silly" and "dumb" are the keywords to getting a response
> today
> :o)
>
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>