I think your question is vague and misleading based on other answer provided. What is SOUNDS like is that you have a database of teachers and students (much like a membership as a gym or similar). For each record in the database, you have an image file associated with that person. The image may be part of the actual table, or just a file name that is pointing to a specific directory on your drive share, where all the people images are available.
From that, these people have ID cards and when they enter a given facility (your Library for example), they run their ID card through a reader. At that time you are doing a search from your network database of users, find the user and pull up the image to the screen to show who the person is to help prevent fraud of someone using somebody else's ID card. This allows the person monitoring the entry area to make sure that Jim is not using "Bill's ID card to gain access.
If this is the case, and your VFP app is already running and ready to read from the card reader, you should only need to add an image file to your screen for presentation somewhere. Then, based on your finding the appropriate ID, get the record, analyze (if part of the record or just file name in a given images path), get the image file and set the property on the image control to point to the correct image. Then, do whatever logging update that states that Bill just entered the facility.
-- update per comment --
Jenna, I don't know how the original records were added to your table, and it sounds like you were handed this project. The column type within VFP is that of a "General" field. Somewhat like that of a memo field that can also hold binary data, the General data type is more for Object Linking and Embedding (OLE) content. It appears that when users were storing the values, they were adding as a linked or embedded content via something like
APPEND GENERAL YourPictureColumn from SomePath\SomeFileName.bmp
check the syntax under VFP 6 for "APPEND GENERAL". You can also state how via a LINK to the actual file vs EMBEDDING by having the actual image included so if the original source is removed, you still have it in the file.
As for the "picture frame" you see when you double-click this column, it is because VFP does not know how to properly interpret the image, such as as "MS.Paint" class object, or "Picture", or whatever. I've never really liked doing General fields, but would instead have a memo field with just the name of the full path/file name of the image I was keeping and had a separate folder to just stick all the image files. Then, when I needed to show that specific image, I would change the property of the image object on the VFP form to that location.
Now, if that is a route you might like to go with, I'm not exactly sure out to extract those image files, but can look into it more.
As for testing the concept of the image sampling, in VFP, make a new folder for a sample form.
Copy in the folder a few images to sample.
Create a simple table with 2 columns...
CREATE TABLE MyPicSample ;
( PersonName c(10),;
ImgSource m )
Add as many records as images you copied to the test folder. For each, put the file name of the images (full path) into the "ImgSource" memo field, and a sample description for the "PersonName".
Next, create a form, open the data environment and add the "MyPicSample" table just created.
Drag this table from the data environment to the form and it will create a grid on the form. Resize it some you only need a small amount of space to show the one column for PersonName. Close the data environment.
Add an "Image" control to the form. It should default the object name to "Image1"
Double-click on your grid to bring up its code snippet window and then double-click on the "AfterRowColChange" event... paste the following over it..
LPARAMETERS nColIndex
Thisform.Image1.Picture = MyPicSample.ImgSource
Save and run the form. As you scroll up/down the grid, you should see the image change to the respective BMP/JPG file.
I think this is the concept of what you want, but instead of a data table grid displayed, you will be doing this from a scanned card that gets a record, has an image and then present THAT image (now in a General data column type).
Again, not sure how you have your images via embedding or linked, but with this, we can probably get going closer to your end-result needed.