>I hope you have some time budgeted for this - otherwise use Edward Pikman's strategy, more or less:
>
>1. Put BMP name in BmpList along with a system ID.
>2. Put a list of numbers and descriptions linked by the BmpList ID.
>3. On right click, pop up the numbers & descriptions.
>
>Otherwise you should write 2 sets of code. One to set up your link table and one to set up your actual screen. The setup program will save the location where you click on the screen and let a user add descriptions. (You pop up a picture, and on a click you pop up a little form. The form requests a description and puts a Shape object on screen. User sizes the shape object and moves it if necessary. Before pulling up a new picture, the program runs through all these shape objects and saves their locations and sizes along with the description in your linking table. That's just for setting up each picture.)
>
>Then in your main application, when the user pulls up a picture, the program should add transparent objects to the picture. These should have an ID property set on them which corresponds to the linking table ID. They should all be of a special shape class that has a clever click action...
>
>Get it? A pain in the tuchus, but fun if you have time.
>
>Adam

Basically what we have already done covers the linking of image to data and
I have been thinking ( and testing )along the same lines as your second suggestion, having one program for our people to display each image and perform set up and a different program for the end user to display image that adds objects based on saved location data. The click of the object would search a table that is keyed on image number plus reference number and display found data. I figured this would end up how we would have to do this, but I was unsure if there was a way to use a general field or foxhwnd.ocx would be of use a make the task smaller.

Thanks to you and Ed !!