EAN-130025195045308   EAN-13 barcode 0025195045308
UPC-A025195045308   UPC-A barcode 025195045308
Product NameBeethoven's Dog-gone Best Movie Pack
CategoryElectronics / Photography: A/V Media: Movie / TV
Short DescriptionWeight:0.25 pounds
Amazon.comA Buy on Amazon ~ B001GZM46Q
Price New10.98 US Dollars    (curriencies)
Price Used2.74 US Dollars    (curriencies)
RatingPG - Parental Guidance Suggested
IMDbNot on IMDb
Run Time662 minutes
Aspect Ratio1.33:1
CastCharles Grodin, Dave Thomas, Jennifer Finnigan, Jonathan Silverman, Judge Reinhold
GenreKids & Family
Run Time662 minutes
Width5.5 inches    (convert)
Height0.6 inches    (convert)
Length7.5 inches    (convert)
Weight40 hundredths pounds    (convert)
FormatMultiple Formats, Box set, Color, Dolby, NTSC, Widescreen
Run Time662 minutes
Long DescriptionGet ready for Beethoven’s greatest hits, a howl-arious, tail-wagging collection the whole family will enjoy. Featuring the bumbling antics of America’s favorite St. Bernard, his adorable brood of cuddly puppies and an all-star cast of owners and friends, the Dog-Gone Best Movie Pack is family entertainment at its dog-gone best with over eight hours of laughter and surprises that’ll really raise the woof! This set contains six fun-filled movies, including the brand-new feature-length comedy Beethoven’s Big Break.
Similar Items9781417041787: Beethoven Family Double Feature
9780783283081: Beethoven's 5th
0883929337798: 4 Kid Favorites Mary-Kate & Ashley Travel the World
0883929135998: 4 Film Favorites: Free Willy (Free Willy, Free Willy 2: The Adventure Home, Free Willy 3: The Rescue, Free Willy 4)
0786936774269: Air Bud Spikes Back
0786936758320: Homeward Bound - The Incredible Journey / Homeward Bound II - Lost In San Francisco
0786936190991: Honey, I Shrunk the Kids
0032429257178: Hotel For Dogs
0025192214028: Beethoven's Treasure Tail
0024543672319: Marmaduke
Modified04-10-2020 3:40:19pm
Search Googleby EAN or by Title
Query Time0.0206599

Article of interest

This describes how to use version 3.x of the data feed. Version 2.x of the feed is still supported. Version 1.x of the feed is no longer supported in any way.

IMPORTANT: Starting with version 3.2, we have a new property and a new way of dealing with product images. Read about it here.

Accessing the data requires your account to have an active data feed. This switch can be turned on or off on the data feed page. This is also where you will be able to view your KEYCODE which is required to make calls to the feed.

Main changes from version 2.x to 3.x include (but not limited to)...

Calls to the data feed are made via HTTP GET or HTTP POST requests. There are only a few required parameters when making a call.

Most other parameters are optional and they will alter the way data is returned to you and how your request is processed. You can also pass in your own values that you need carried through. Any parameter that the system doesn't recognize will be returned AS-IS in the status block. This can be handy in situations where you are pulling the data in an asyncronus manor and need extra information passed into your callback routine.

When performing a lookup...

When updating data...

When deleting data...

There are some special "get" operations that need no other parameters. You would not use "find" or "update" when using these. Only use the "keycode", "mode" and "get" for these items. These operations are important because many of our elements are data driven and that data changes over time. We normally don't remove attributes or categories but we do often add to the collection.

The returned data can come back in JSON or XML format. In either case the structure of the data is the same. Because it is easier to read, we will be using XML to demonstrate the layout of the result. Here is the data layout. Notice that this is a complex object and some elements have child elements and some elements may be arrays with repeating content.

The easiest way to get the feel of the data is to make several requests using your web browser and ask for the data in XML format. Although JSON is often easier to work with in code, the XML output is often easier for people to read because of the nice markup tags that wrap around each element and the web browser will usually do a nice job of indenting to make it clear which elements are stored within other elements.