Help using bound images in data access pages

[Guest]

First, I'll paste the help article that is not to helpful, then I'll ask my
question:

""""""""""Add a picture or object that changes from record to record
You can use an image control to display a bound picture in a form, report,
or data access page. To display a bound embedded or linked picture or object
on a form or report, you must create a bound object frame.

Add a bound image control

Do one of the following:
To display pictures that change from record to record without storing them
in a table, create a text field to store the locations of the image files.
You must store the locations of the pictures in a text field if you want to
display the pictures in a data access page. You can also use a text field to
store the location of pictures and then use those pictures in a form or
report, but you must use Visual Basic event procedures to display the
pictures. """""""""


MY QUESTION:
What is, or how do I create a "Text Feild?" and how does that bind a
particular image to a record?

I serious want to figure this out.. If you can help.. that would be great!

In reality... why isn't this feature just built in to use images in data
access pages?

I am using version 2002
Brian Maloy

 

[Larry Linson]

MY QUESTION:
What is, or how do I create a "Text Feild?" and how
does that bind a particular image to a record?

A Text Field is one of the types of Field you can define in a Record in a
Table. Its purpose is to hold, yep, you guessed it... text information (the
variable type for holding text is a "String" variable).

Into this Text Field, you store the fully-qualified (aka "well-formed") path
and file name of a file containing an image, and that 'binds' the image file
to the Record.

I serious want to figure this out.. If you can help.. that would be great!

In reality... why isn't this feature just built in to use
images in data access pages?

Data Access Pages were limited in functionality, and only really useful in
intrAnets, where the software on the using computers could be controlled.
As a result, they never became very popular, and Microsoft has stated that
DAP will be "deprecated" in Access 2007... that is, you are advised not to
do new development using DAPs, and Access 2007 will not support creating a
new DAP nor maintaining an old one. It will support running an existing
DAP.

Thus, I guess we'll never know. Of course, we never know why Microsoft
makes their design decisions, anyway. They (quite rightfully, IMNSHO) do
not feel obligated to explain either why they did something, or why they did
not do something. So, such questions tend to be fruitless when asked in
newsgroups.

For using pictures in MDB (not DAP and not ADP), I have some information at
http://accdevel.tripod.com.

Larry Linson
Microsoft Access MVP