Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 7148 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies
Posted

I have a database containing all the shots from a film I am working on. I have successfully updated my datatbase by importing a continuity list containinng information reagarding what section of each shot is used in the cut and where it is located in the cut. I run into problems however, if a shot is used multiple times. In such cases I would like each occurence of the shot to be a unique record with a unique shot name.

For example: "Shot A" exists in my current database. I then import a continuity list containing how much of each shot is used and when it is used in the film. "Shot A" is used only one time. "Shot A" is then updated to contain continuity information. Portions of "Shot B" appear on the continuity list 2 different times. I would like the Database to create 2 different records titled "Shot B_01" representing the first appearance of "Shot B" and "Shot B_02" for the second occurence of "Shot B". Both "Shot B_01" and "Shot B_02" should contain all of the original data from "Shot B" as well as their respective continuity information.

Any help would be greatly appreciated!

Posted

I believe you need a relational structure. Two tables; one for Shots (A, B etc as records) and one for your Continuity List. As you've said ... "Portions of "Shot B" appear on the continuity list 2 different times. "

You are attempting to mix a 1:n (one-to-many). You are importing into the Continuity List (with many Shot B records) for example. If so, then join to a Shot table on the ShotName.

It's difficult to pinpoint but you may need to script breaking your import apart after it's finished (or even use an intermediate import table to hold the fresh import for parsing). Multiple *same* Shot names imported into fields then split them again (turn them into records). I am unclear on the data coming in - and the resultant fields available. Can you post an example of both import and existing table structure? I think that would help us alot here.

Once the new Shot records are created, you can number your Shots with a unique ID (or use Auto-Enter when creating them). Again, it would depend upon what you have and want.

This topic is 7148 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.