Scrolling Container Fields

[Delights]

Greetings:

I am running a database for my Adult shop, there is thousands of record. Each record holds information on a particular title. Each Title has it's own record.

There is a Container field called "Image" which is on the database, i have also made 2 other Containers called "Image-front" and "Image-back".

I have also put arrows below the container field.

What i want to do is make it so that when you click on the right arrow it shows "Image-back" in the container field "Image" and when you click the left arrow, it puts "Image-front" in the container "image".

Also i would like the Container field "image" to already show the image from "Image-front" automatically.

So you goto the record. Image front is in the container "image" you click on the right arrow it shows "Image-Back" in the container "image" then click on the left and it shows "Image-front" in the Container "image".

There is a way of doing it with different records, however i am using records to hold the details on the DVD's.

I was trying a way to make it so that when you click on the right "image = Image-back" and when you click on the left "image = Image-front".

Is there a way of making it work ?

[Fenton]

First, I would put the images in their own table. If they are large, their own file (I don't like keeping large images in the same file as the data, makes it difficult to swap files with a client, and I don't entirely trust images; little ones are fine).

This would mean they'd need a relationship to their parent record. Then they'd need a Type text field to contain "Front" or "Back".

On the parent layout you'd have a single container field. It would be based on a relationship from the parent ID to the the images Parent ID foreign key, AND a global text field in the parent file to the "Type" field in Images.

A single script would do both. Each button would pass a Script Parameter, either "Front" or "Back." The script would simply set the global Type field, then Commit Record. It could possibly just be a single step attached to the button, as the container would likely not be enterable on this layout.

The reason to use the Parent ID instead of a global Parent ID is so if you switched records somehow, you'd at least see one of the correct pictures. It is impossible to "automatically" show the Front picture, unless you control navigation from record to record with a script, to set the global back to "Front" (if it was "Back").

I suppose you could make the Type field also a regular field, not global; then they'd only screw up 1 record if they left it as "Back". But a navigation script is not difficult. You have to Hide the Status Area however.

ThumbsFrontBack.zip