Image
EAN-130012569797840   EAN-13 barcode 0012569797840
UPC-A012569797840   UPC-A barcode 012569797840
Product NameViva Las Vegas
CategoryElectronics / Photography: A/V Media: Movie / TV
Amazon.comA Buy on Amazon ~ B000QUUD56
Model2287103
Price New6.97 US Dollars    (curriencies)
Price Used2.51 US Dollars    (curriencies)
RatingPG - Parental Guidance Suggested
IMDbIMDb Link
TrailerWatch The Trailer
Run Time85 minutes
Aspect Ratio2.35:1
CastElvis Presley, Ann-Margret, Cesare Danova, William Demarest
DirectorGeorge Sidney
GenreCOMEDY,MUSICAL
Run Time85 minutes
Width5.5 inches    (convert)
Height0.53 inches    (convert)
Length7.5 inches    (convert)
Weight36 hundredths pounds    (convert)
BindingDvd
Release Year1964
FormatMultiple Formats, AC-3, Closed-captioned, Color, Dolby, NTSC, Original recording remastered, Restored, Subtitled, Widescreen
Run Time85 minutes
FeaturesShrink-wrapped
Long DescriptionLucky Jackson arrives in town with his car literally in tow ready for the first Las Vegas Grand Prix - once he has the money to buy an engine. He gets the cash easily enough but mislays it when the pretty swimming pool manageress takes his mind off things. It seems he will lose both race and girl, problems made more difficult by rivalry from Elmo Mancini, fellow racer and womaniser. Perhaps some singing will help.
Similar Items0012569798809: Double Trouble
0012569797833: Jailhouse Rock
0012569797550: Stay Away, Joe
0012569797536: Kissin' Cousins
0012569797529: Girl Happy
0012569791190: Elvis harum scarum The trouble with girls
0012569703728: Elvis Presley - The Signature Collection (It Happened at the World's Fair / Speedway / Spinout / Harum Scarum / Jailhouse Rock / Viva Las Vegas)
0012569518421: Trouble With Girls
0012569517820: Spinout
0012569506121: Jailhouse Rock
View 22 more similar items
Created05-22-2010
Modified03-17-2019 7:31:28am
MD5dd47fcee331f88052ad9b99a3685b9b7
SHA25626230331bbc1e8536d7c6400c95d7522e9a8cc0ae9489fad9f87883288d74542
Search Googleby EAN or by Title
Query Time0.0203540

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.

Close

Search

Close

Share

Close

Dialog