Use 160GB through iTouch interface?

Situation: I love the iTouch (I have the 16GB, preordered before they hit the market), but it has far from enough space to hold my music (300+GB). I also have a 160GB iPod Classic... is there any way to connect the two so that I can have 176GB total space, but use only the iTouch interface to go through it all?
The scroll wheel on the iPod classic *****, to be honest. It's not very sensitive. I don't want to "degrade" (so to speak)... but I also want to carry all my music on a player that is fun and easy to use? Thanks!
P.S.: I've thought about this a lot, and my guess is that the answer is going to be a short "No." So, I ask: Why not? I've spent upwards of $500 for these products, and feel that because of my investment I am right to expect convenient and useful things like this to be possible, even if said versatility is not emphasized or even mentioned (as Apple would much rather that I spend another $200-$300 on a brand new iTouch with hardly any space).

Sorry, no you can't. I would assume that having a touch screen product to run iOS with a hard drive which can hold that much space(instead of flash drive) would be too big(brick) and costly. Maybe someday if flash memory increases greatly but that is no where in sight.
It is just two different devices. Harddrive v. flash drive. Since apple is moving all their new products to be touch based I don't expect any new product with large amounts of memory.
There is a reason that the ipod touch can go to 64GB and the iphone can only go to 32GB. It is because of space. The ipod touch can just fit another 32GB in the space that phone parts would go.

Similar Messages

  • I upgraded to mavericks About a month ago, Every since I have had pops and static when playing anything through quicktime nd when playing sound cloud through Safari. I am using a presonus Firestudio interface. What can i do to correct this?

    Hey all,
              About a month ago I upgraded to mavericks on my 2009 imac. I am using a presonus firestudio interface. Every since quicktime will not play without massive static, It gets better when I change to 48,000 but still there. also safari will not play music or videos that use quicktime. How can i solve this or go back to mountain lion which worked flawlessly.

    Hey all,
              About a month ago I upgraded to mavericks on my 2009 imac. I am using a presonus firestudio interface. Every since quicktime will not play without massive static, It gets better when I change to 48,000 but still there. also safari will not play music or videos that use quicktime. How can i solve this or go back to mountain lion which worked flawlessly.

  • Why do I get -18001 Errors using Customised TestStand User Interface

    Hi all
    I have a problem when attempting to run my application on my host NT PC. I have a customised operator interface to TestStand written using Labview 5.1.1 and built using the LabVIEW application builder. I am running the TestStand Development (Run-Time) System on my host PC.
    The problem is that as soon as I go to run my sequence of vis (mass compiled using the same version of LabVIEW and assembled for run-time distribution) I receive the error '-18001 VI Not Executable.'
    I think this is probably to do with how I've included the ActiveX server in my LabVIEW User Interface application, but knowing very little about ActiveX I'm not sure exactly what the problem is.
    If anyone
    has any ideas, I would be extremely grateful for any assistance you could offer. My TS version is 1.0.1
    Thanks
    Dave

    David,
    I would like to add to Richard's input. The typical reasons a VI cannot be executed that cause this message are:
    1) There is an error in the VI such that the run arrow of the VI is broken when the VI is open in the LV development environment. This problem is usually easy to debug because you should get the error (shown below) when running your sequence in the sequence editor using the default "LabVIEW" ActiveX server provided by the LV development environment (not the LV ActiveX server provided by your operator interface which is by default named "TestStandLVGUIRTS" ).
    An error occurred in the 'MyVIStep' step of the 'MainSequence' sequence in 'MySequence.seq'.
    LabVIEW : VI is not executable.
    An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001
    2) The same error will occur when
    a. you are using any LV ActiveX server other than the "LabVIEW" server provided by the LV development environment, AND
    b. at least one of the called VI was not assembled for distribution properly. This means that not all test VIs and their *entire* hierarchy were distributed.
    I am not sure exactly what you have done so have compiled some information that I think will help. Below I have included the document, Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter, which will appear in the NIDZ shortly. Another useful document is the NIDZ document Distributing LabVIEW Test VIs, which you can obtain from our website. Read these documents before preceding with the steps immediately below, which give you an example process for distributing. This may help provide a better understanding and guidance in the distribution process. We are working to simplify this process in future versions of TestStand.
    For the following example distribution I recommend that you are use default shipping code so that the problem is not complicated with potential errors added through customizations you have made.
    Building The Operator Interface
    The following are steps if you are using a LabVIEW operator interface.
    1) Copy the contents of \OperatorInterfaces\NI\LV to \OperatorInterfaces\User\LV.
    2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
    3) In LabVIEW Select Tools>>Build Application or Shared Library
    4) In the builder click the Load button and load \OperatorInterfaces\User\LV\testexec.bld. This build script is configured to create testexec.exe that contains the LV ActiveX server with the name of TestStandLVGUIRTS (see the Application tab of the builder).
    5) In the builder click Build.
    6) Once the application testexec.exe is built, run it once so that the server TestStandLVGUIRTS is automatically registered. You do not need to run a sequence. Close texec.exe.
    Creating a LabVIEW Run-time Server
    If you are using the LabVIEW operator interface then skip this section. The following steps are meant for those who use an operator interface written in a ADE other than LabVIEW. They provide you with a LabVIEW run-time server that is used by TS to run your VIs.
    1) Copy the contents of \Components\NI\RuntimeServers to \Components\User\RuntimeServers.
    2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
    3) In LabVIEW Select Tools>>Build Application or Shared Library
    4) In the builder click the Load button and load \Components\User\RuntimeServers\LabVIEW\TestStandLVRTS.bld. This build script is configured to create TestStandLVRTS.exe that contains the LV ActiveX server with the name of TestStandLVRTS (see the Application tab of the builder).
    5) In the builder click Build.
    6) Once the application TestStandLVRTS.exe is built, run it once so that the server TestStandLVRTS is automatically registered on your development machine. Close TestStandLVRTS.exe.
    Assembling the Test VIs for Run-Time Distribution
    This distribution process uses one of the shipping TS examples that calls LV VIs.
    1) From LV mass compile all VIs in the directory \Examples\AccessingArrays\UsingLabVIEW\. Please make sure that there were no error messages in the Status tab of the Mass Compile dialog box.
    2) In the sequence editor open \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq
    3) Confirm that the sequence runs without problem.
    4) In the sequence editor select Tools>>Assemble Test VIs for Run-time Distribution.
    5) If you are using TestStand 2.0 select \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq as the file from which the VIs should be assembled.
    6) Set the target directory to be something distinct like C:\temp\AssblVIs.
    7) If you are using TestStand 2.0 skip adding Dynamic VIs
    8) Save with or without diagrams. Its your choice.
    Change Search Directories
    Once the VIs are assembled successfully, you must add the new target directory to the TS search directories.
    1) In the sequence editor select Configure>>Search Directories.
    2) Add your target search directory (e.g. C:\temp\AssblVIs) to the search directories.
    3) Close the Edit Search Directories dialog box.
    4) Confirm that your sequence steps now reference the assembled VIs. Right click on a step in the sequence and select Specify Module.
    5) The dialog should show that the code module is found in the target directory (e.g. C:\temp\AssblVIs) that you just added to the search directories.
    6) Run the sequence. This is the initial test to see if the VIs are assembled properly.
    Switch the LV Adapter to use the TestStandLVRTS server or TestStandLVGUIRTS
    1) In the sequence editor select Configure>>Adpaters.
    2) In the Configurable Adapters control select the LabVIEW Standard Prototype Adapter and then click the Configure button.
    3a) If you are not using the LV operator interface then switch the ActiveX server to TestStandLVRTS.
    3b)If you are using the LV operator interface then switch the ActiveX server to TestStandLVGUIRTS.
    4) Close the adapter configuration dialog boxes. You will get a couple of questions boxes. Just click OK each time.
    5) Now run your sequence. If successful you are no longer using the LV development environment to run your VIs. This shows that the VIs were assembled correctly, the LV ActiveX server is working properly and that the search directories are configured properly.
    You can now try and run the sequence using your operator interface on you development computer. If this test works it means that you have also confirmed that your operator interface is working correctly with all the other components. Now it is just a matter of moving all the component correctly to the target machine.
    Distributing Components
    -To distribute your operator interface use the distribution tool of the application development environment (ADE) in which you built your operator interface.
    -To distribute the TS engine using the Run Engine Installation Wizard tool. This tool is typically not used for distributing your sequences and VIs, which you will probably distribute more frequently than the TS engine. It does distribute and register your LV run-time server (if you are using one) as long as you have stored it in \Components\User\RuntimeServers. It also distributes other TS components that you have stored under the directory \Components\User\.
    -You can use whatever distribution system you like to distribute your VIs and sequence files (e.g. ZIP and network transfer are popular) . Ensure that you distribute the assembled VIs and not the development VIs. Also ensure that the location of the VIs on the target machine is one of the TS search directories.
    Hope this helps.
    Regards,
    Kitt
    =========================================
    Title:
    Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter
    The general outline of the components to be distributed and the actions to take are followed by a more detailed description.
    Components that need to be distributed:
    TS engine
    Operator interface
    LabVIEW executable that will act as a LabVIEW ActiveX automation server (If the operator interfaces is written in LabVIEW, it can function as the LabVIEW ActiveX automation server.).
    LabVIEW run-time engine
    LabVIEW test VIs
    Test sequence files
    Actions before distributing:
    It is recommended that you test the distribution components on the development machine before you distribute them to your target machine. In this manner you can more easily debug errors that you may encounter
    Create the executable that will serve as your LabVIEW ActiveX server on the target machine (components 2 or 3 above).
    Assemble the test VIs for distribution.
    Update the TestStand search directories so that the sequences reference the assembled VIs.
    Configure the LabVIEW Standard Prototype Adapter to use the LabVIEW ActiveX server that you will install on the target machine.
    Test the distribution components on the development machine.
    Enter section headings, separating each section with a line break:
    TS Engine Component
    Operator Interface Component
    LabVIEW ActiveX Server
    Configuring the LabVIEW Standard Prototype Adapter
    LabVIEW Run-time Engine Component
    Assembling your Test VIs for Distribution
    Note
    TS Engine Component
    With any TestStand distribution you must install the TestStand runtime engine on the target machine. The Run Engine Installation Wizard tool, found under Tools menu of the Sequence Editor, facilitates this process. The wizard tool will create two files, SetupTSEngine.exe and TSEngine.cab. Move the two files to your target machine and run SetupTSEngine.exe to install the TestStand engine.
    These installation files include the current configuration settings that exist in the Sequence Editor at the time the tool is invoked. It also includes all process models, TestStand types and step type modules. If you have customized components of TestStand and saved them under the directory TestStand\Components\User, then the components will also be included with the engine installation.
    You must purchase at least a base deployment or debug deployment license for each machine on which you install the TestStand engine.
    Operator Interface Component
    You will also need to install an operator interface executable on the target machine. This program acts as a client to the TS runtime engine, controlling the execution of sequences and displaying their progress. TestStand ships with several versions of TestStand operator interfaces, which are written in different application development environments (ADE). For distributing the operator interface executable, refer to the application development environment in which it was created.
    LabVIEW ActiveX Server
    You must have a LabVIEW ActiveX server on the target machine. TestStand uses the LabVIEW ActiveX server to run VIs using either the LabVIEW development environment or the LabVIEW runtime engine. The LabVIEW ActiveX server is provided by either LabVIEW development environment or by any LabVIEW executable that has been built with �Enable ActiveX Server� selected. This setting can be accessed in the LabVIEW Application Builder during the build process. When this preference is enabled, you must enter a server name. You will use the server name to configure the LabVIEW Standard Prototype adapter in TestStand.
    If your operator interface is written in LabVIEW, then it can act as the LabVIEW ActiveX server on your target machine. TestStand ships with two operator interfaces written in LabVIEW. The standard LabVIEW operator interface is located in TestStand\OperatorInterfaces\NI\LV, while a simplified version is located in TestStand\Examples\OperatorInterfaces\Simple LV. LabVIEW buildscripts are provided for these applications to facilitate building an operator interface in the latest version of LabVIEW. The settings of these buildscripts are such that the applications are LabVIEW ActiveX servers with the server names of TestStandLVGUIRTS for the standard operator interface, and TestStandSimpleLVGUIRTS for the simple operator interface. The applications register the servers the first time they are executed. If you want to manually register or unregister one of the servers, you can invoke the executable with the /RegServer and /UnregServer command-line arguments respectively.
    If your operator interface is programmed in a language other than LabVIEW, then you will need a separate LabVIEW executable to provide the LabVIEW ActiveX server on your target machine. For this purpose, TestStand ships with a LabVIEW run-time server application located in TestStand\Components\NI\RuntimeServers\LabVIEW. A LabVIEW buildscript is provided for this application to facilitate building a run-time server in the latest version of LabVIEW. The settings of this buildscript are such that the application is a LabVIEW ActiveX server with the server name of TestStandLVRTS.
    Note: When an ActiveX executable server is accessed, the executable is launched automatically if it is not already executing.
    Configuring the LabVIEW Standard Prototype Adapter
    When TestStand runs a VI using the LabVIEW Standard Prototype adapter, it does so using a LabVIEW ActiveX server. By default the adapter is configured to use the �LabVIEW� server, which is provided by the LabVIEW development environment. If you do not have the LabVIEW development environment on your target machine then you must configure the LabVIEW Standard Prototype adapter within TestStand to use a different server (e.g. TestStandLVGUIRTS, TestStandLVRTS, or TestStandSimpleLVGUIRTS).
    To configure your LabVIEW Standard Prototype adapter, select Configure>>Adapters from the menu. In the Adapter Configuration dialog box that appears, select the LabVIEW Standard Prototype Adapter in the Configurable Adapters section. Click the Configure button. You can select or type a server name in the Select or Type Which LabVIEW ActiveX Server to User control. If your server name is not in the list you will need to type it.
    As explained in the LabVIEW ActiveX Server section above, TestStand ships with LabVIEW buildscripts to build a LabVIEW operator interface and a LabVIEW run-time server application. These applications are LabVIEW ActiveX servers with server names TestStandLVGUIRTS and TestStandLVGRTS, respectively. You can configure you LabVIEW Standard Prototype adapter to use one of these servers.
    LabVIEW Run-time Engine Component
    If any of your sequence steps use the LabVIEW adapter or if your operator interface is written in LabVIEW, then you must install the LabVIEW runtime engine on the target machine. It is important that your LabVIEW run-time engine is the same version as the VIs that TestStand executes.
    You can find installation files for the LABVIEW 5.1 run-time engine in the LabVIEW installation directory, Labview\APPLIBS\installs\RunTime. In addition, you can choose to automatically distribute and install the LabVIEW run-time engine with the distribution of a LabVIEW executable. Refer to LabVIEW documentation.
    Assembling your Test VIs for Distribution
    After distributing TestStand, you must ensure that your sequences are able to locate the VIs they call, and the VIs must be able to locate their required resources.
    One common mistake is to simply copy the original VIs from the development machine to the target machine. Once you have configured your LabVIEW Standard Prototype adapter to use a LabVIEW ActiveX server other than LabVIEW, your sequence will not be able to execute your original test VIs that your sequences call.
    TestStand provides the Assemble Test VIs for Distribution tool, which gathers test VIs and their required resources, and places them in a common location for distribution. You can then modify your TestStand search directories so that your sequences reference the assembled VIs. These topics are covered in the NIDZ document Distributing LabVIEW Test VIs.
    Links: See Distributing LabVIEW Test VIs below
    Note
    Remember to test your distribution components on your TestStand development system before distributing TestStand. If the execution does not work on the development system it is not going to work on your target machine. On your development machine you have more ability to debug problems you may encounter.
    Note: One common problem of testing distribution components on your TestStand development system is that your sequences reference the original Test VIs instead of the assembled test VIs. Refer to the NIDZ document Distributing LabVIEW Test VIs for assistance.
    Once the components work on your development machine, you are ready to install them on your target machine. The order in which you install these components on the target machine is irrelevant.
    ==============================================

  • IPod touch won't charge while installed in vehicle through direct interface

    Hello,
    This just began happening about two weeks ago. The touch won't charge while installed in the car directly through the interface. I have tried three different set-ups so I know it is not the iPod cable or stereo. It seems to charge and hold said charge fine through wall plug or CP but while in the car it only seems to charge enough to continue playing and then when the car is off, it acts as though it is no longer connected and dies so when I start the car the next time, I have to wait for the unit to charge enough to play...
    Oh and it is a 1st gen 8gb touch.
    Is this the battery or a hardware issue with the touch itself?
    Thanks for any help...
    Nick

    I have the same problem with my Audi and started when I installed the 3.0 update. Besides I can't use the Hi Fi Apple device, which I bought 3 years ago. I'm sure the update didn't take in considerations old interfaces and the HiFi.
    32gb
    2nd gen

  • Able to edit Business Rules through Excel interface?

    Hi,
    I wonder if there is any way that I can add, modify or delete the Business Rules definitions through Excel interface. In the Admin Console, though the Business Rules interface looks neat, I encounter the following difficulties in editing the Account Transformation definitions:
    1. The check in the Reverse Sign sometimes disappears after the definitions being saved. I have to click something other than Business Rules, like Dimensions, Application, Security, etc, and come back to Account transformation again in order to have the Reverse Sign check being saved.
    2. I'm not able to to check the Reverse Sign in the last definition of Account transformation. It always disappears after being saved. My workaround is to put a dummy definition at the end or not to put that definition, which needs Reverse Sign, at the end.
    3. When I delete some definitions in the middle, the following error pops up after validation.
    [] value does not exists in ID of Account dimension.
    4. I have written my definitions in my design documents in Excel but I'm not able to copy and paste all of them to Admin Console's business rules. I have to fill in each value one by one.
    Or can I simply edit the table dbo.clcCALCAccount_XXXX? Since I used to be a database programmer, I feel it easier to directly edit the database table rather than using the business rules interface.
    Best Regards,
    Sunny

    Sunny,
    It is not according to the book but it is possible to change the business rules directly on the SQL. That is the way i do it sometime... and yes the table you point is the right one. You see other tables for other business rules...
    Usually i just do a copy and paste into excel. Then i change into excel (i also use EVPROs to check if the members are not calculated members...) and then i repaste it into SQL...
    But I have to say, do it at your own risk, as I stated before it is not really advised/safe...
    Nic

  • Sending Data from BI to Third Party System through CIB Interface

    Hi Experts ,
    We have a requirement where we need to send data from BI to any Third Party System through CIB Interface . We do not have to use the OHD's . Please share the documents for the same .
    Regards
    Garima

    Hi,
          My problem is solved.
    Sol:  Getting wrong data from third party sytem. They are adding spaces in front of the payload and end of the payload so it was not processing. After deleting that spaces its is working fine.
            Thanks for your help.
    Thanks & Regards,
    Purshothamm

  • Cisco 4402 WLC IOS Upgradation using CLI and Web Interface

    Hi,
    I would like to know how to upgrade IOS of Cisco 4402 WireLess LAN Controller using CLI and Web interface ?
    Can any one help me regarding the same.
    Please answer as soon as possible.
    Thanks in advance.

    Here are the instructions for upgrading the controllers via GUI:
    http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn52.html#wp472449
    Instructions via cli:
    Cisco recommends that a direct CLI console port connection is used to update the controller software.
    1. Make sure a TFTP server is available for the Operating System (OS) software download. Also, keep these guidelines in mind when the TFTP server is set up:
    If a download is performed through the service port, the TFTP server must be on the same subnet as the service port because the service port is not routable.
    If a download is performed through the Distribution System (DS) network port, the TFTP server can be on the same or a different subnet because the DS port is routable.
    The TFTP server cannot run on the same computer as the Cisco Wireless Control System (WCS) because WCS and the TFTP server use the same communication port.
    2. Download the desired OS software update file from the Cisco website to the default directory on the TFTP server.
    3. Log into the WLC CLI.
    4. Issue the ping server-ip-address command to verify that the WLC can contact the TFTP server.
    5. Issue the transfer download start command and answer n when prompted to view the current download settings.
    This example shows the command output:
    transfer download start
    Mode........................................... TFTP
    Data Type...................................... Code
    TFTP Server IP.................................
    xxx.xxx.xxx.xxx
    6. TFTP Path...................................... TFTP Filename.................................. AS_2000_3_0_x_x.aes --OR-- AS_4100_3_0_x_x.aes --OR-- AS_4400_3_0_x_x.aes Are you sure you want to start? (y/n) n Transfer Canceled Issue these commands to change the download settings:
    * transfer download mode tftp
    * transfer download datatype code
    * transfer download serverip tftp-server-ip-address
    * transfer download filename filename
    * transfer download path absolute-tftp-server-path-to-file
    Note: All TFTP servers require the full pathname. For example, in Windows, the path is C:\TFTP-Root. (In UNIX forward slashes (/) are required.)
    7. Issue the transfer download start command to view the updated settings, and answer y when prompted to confirm the current download settings and start the OS code download.
    This example shows the download command output:
    transfer download start
    Mode........................................... TFTP
    Data Type...................................... Code
    TFTP Server IP.................................
    xxx.xxx.xxx.xxx
    TFTP Path......................................
    path>
    TFTP Filename..................................
    AS_2000_3_0_x_x.aes --OR--
    AS_4100_3_0_x_x.aes --OR--
    AS_4400_3_0_x_x.aes
    Are you sure you want to start? (y/n) y
    TFTP Code transfer starting.
    TFTP receive complete... extracting components.
    Writing new bootloader to flash.
    Making backup copy of RTOS.
    Writing new RTOS to flash.
    Making backup copy of Code.
    Writing new Code to flash.
    TFTP File transfer operation completed successfully. Please
    restart the switch (reset system) for update to complete.
    8. The WLC now has the code update in active volatile RAM, but the reset system command must be issued to save the code update to non-volatile RAM (NVRAM) and reboot the WLC.
    This is a sample output:
    The system has unsaved changes.
    Would you like to save them now? (y/n) y
    The controller completes the bootup proce

  • Use WLC's service interface IP when add WLC into WCS

    Hi All,
    Does anybody know if there's any limitations or bugs to use WLC's service interface IP when add WLC into WCS?
    Another question is I remember there's a post previously says that there are a bug regarding to ARP if the WLC not using LAG but connect one port to one switch, connect another port to another switch, so that's why it is strongly suggested to use LAG, but I can't find it now, anybody know it? Thanks!

    The service port is controlled by the service-port interface and is reserved for out-of-band management of the controller and system recovery and maintenance in the event of a network failure. It is also the only port that is active when the controller is in boot mode. The service port is not capable of carrying 802.1Q tags, so it must be connected to an access port on the neighbor switch.
    If the service port is in use, the management interface must be on a different supernet from the service-port interface.
    The service-port interface controls communications through and is statically mapped by the system to the service port. It must have an IP address on a different supernet from the management, AP-manager, and any dynamic interfaces, and it cannot be mapped to a backup port. This configuration enables you to manage the controller directly or through a dedicated operating system network, such as 10.1.2.x, which can ensure service access during network downtime.
    The service port can obtain an IP address using DHCP, or it can be assigned a static IP address, but a default gateway cannot be assigned to the service-port interface. Static routes can be defined through the controller for remote network access to the service port.

  • Using Webservice through RFC Func Mod Can I able to fill dropdown field

    Hi,
    I am going to develop offline interactive form using Webservice through RFC Function module.
    There are dropdown list fields in my adobe form. Then how can I able to fill these dropdown fields in my form, I mean how to bind the values to dropdown fields.
    Thanks & Regards,
    nspkumar.

    Hi,
    Option 1:
    If the form is designed in transaction SFP, which has a form interface (transaction SFI), then below solution will work:
    For example consider the data node name as 'COUNTRY' . Select drop down UI element and go to 'Object' properties tab. Select 'Binding' tab, on the top right hand side of this tab there is small icon, select the icon and enable the option 'Show Dynamic Properties'. Once this option is enabled in the 'Binding' tab you can click on the link 'Specify Item Values'. A popup will open, here specify the binding value as 
    $record.sap-vhlist.COUNTRY.item[*]
    Refer to link:
    [Drop down list binding|http://help.sap.com/erp2005_ehp_06/helpdata/en/43/7a667df4ad6fc9e10000000a1553f6/frameset.htm]
    Option 2:
    If the data connection is directly to the webservice then binding needs to be done similar to option 1 except one change. While binding the value in dynamic properties based on XML schema binding needs to be changed.
    As you can see in option 1, for dynamic property binding 
    $record.sap-vhlist.COUNTRY.item[*]
    , there is a value called sap-vhlist. This 'sap-vhlist' gets generated when form is designed in transaction SFP with form interface. So in your case if data connection is from webservice value sap-vhlist needs to changed to the value as per XML schema definition.
    Regards
    Srikanth KV

  • Can we use applets as user interfaces with sockets, RMI and J2EE

    Dear Sir or Madam,
    Since I am a TA for software architecture class, some one ask me the following question: I think the answer is "No" based on the document on http://java.sun.com/sfaq/
    How I answer the quesions? Looking forward your help!!!
    1.You may have 2 applets and 2 html files. One applet with one html file may stay at a client PC and run on this PC, and the other applet with the other html file may stay at a server PC and run on this PC. In this case, all the applets are run locally.
    2.Could applets works with sockets, RMI and J2EE?
    3.Can we use applets as user interfaces with sockets, RMI and J2EE?
    Thank you very much!
    Best regards,
    Jing

    The scenario you paint doesn't quite make sense. The "server PC" wouldn't be running an applet, normally, since applets are by definition in a web browser page, and most likely involve user interaction, and "server processes" generally are done without user interaction.
    The security rules around applets are that -- by default -- applets can connect with sockets ONLY to the server from whence the applet was loaded. RMI uses sockets (J2EE is too broad a spec) and hence RMI calls would also be limited to the server from whence the applet was loaded. Within that limitation, an applet could open all the sockets it wants, so long as they are all on the server from whence the applet was loaded.
    If you want two applets on two different systems to communicate with each other, the simplest way is to have them rendevous through a server process on the server(s) from whence each applet was loaded. Maybe it's PC-a <-> server-a <-> server-b <-> PC-b ...? Or maybe PC-a and PC-b both are talking to the same server.
    The limitation is rooted in the security subsystem. You can specify a policy file and override anything in the security subsystem. That does mean signing the applet and then cajoling the user into agreeing to grant greater levels of security than the default. In such a case you can open sockets more broadly and then PC-a could talk directly to PC-b without going through any servers.
    - David

  • How to Hear Metronome in Headphones While Recording Through Audio Interface - Help!

    Hey everybody,
    So I've been trying to work through this problem for 3+ hours now and I'm stumped. It's very frustrating as it is such a simple problem. Right now I'm recording acoustic guitar through an audio interface - guitar sound goes to microphone, microphone goes to interface, interface goes to audio jack in Macbook. Pretty simple setup. I can even insert a splitter into the audio jack on the Macbook which will allow me to hear what I am playing through the interface in my headphones, which is what I wanted. However, when I hit record and the metronome starts playing, as I want it to, I can't get the metronome to play through my headphones - they will only play through the speakers. How can I get around this? Is it even possible, or do I need an audio to USB interface so I can have a set audio in (through the USB) and a set audio out (through the audio port)? Again, your help would be much appreciated as I am completely stumped.
    Cheers!

    In Logic Pro 9 (and X) you can assign different devices to the In- and Output, so I don't understand why you wouldn't be able to get sound in through the microphone and out through the headphones. You can even combine the ouputs into a Multi-Output device to send the same sound simultaneously to all outputs.
    You can also aggregate all your in- and outputs into an Aggregate Device, then you can use any of your outputs and any of your inputs inside the same Logic project (on the channel strips).
    Setup in Audio MIDI Setup (separate app, part of any OS X install, can be found in the Applications>Utilities folder)
    Setup in Logic Pro>Preferences>Audio>Devices (apart from colorscheme, it's the same in LP 9 and LP X)

  • Managing ASA5510 using ASDM via internal interface

    Hello
    I am currently managing an ASA5510 using ASDM through the management port but I would like to manage the ASA through the internal port.
    My concern is that I thought I remembered reading someplace that if you setup an internal port for management that it can't be used for anything else.  Is this correct?
    I only configured one internal port and it is the path to my LAN.  I would hate to configure the port for management only to find that I disconnected my firewall from my internal network in the process.  Can I use my one and only configured internal port for both ASA management and route from my LAN thru the ASA firewall?
    I currently have the management port set to 192.168.1.1 and my internal interface is 10.1.1.1.  If I open ASDM and connect thru the management port and select Configuration/Device Management/Management  Access/ASDM/HTTPS/Telnet/SSH
    select "ADD"
    select access type "ASDM/HTTPS"
    select interface "internal"
    IP Address   "10.1.1.0"
    Mask       "255.255.255.0"
    Will that give me access to ASA management thru my internal network but cripple my network access to the ASA? 
    Sorry if this is confusing... I don't know how else to phrase it.
    Thanks
    Ed

    Hi
    it sounds like a better plan than opening up for each and every unit on the inside :).
    But if you have a old laptop or something like that I would state that setting that up with a syslog server and use that to manage the firewall would be a even better option.
    that way you would get logs and a management station.
    there are several syslog servers that are free and I like to use grep that is also free to filter information.
    http 10.1.1.52 255.255.255.255 inside
    will make the 10.1.1.52 the only server to work with asdm
    but you will have to remove the old http 10.1.1.0 255.255.255.0 inside statement.
    If you find the answers helpful please rate.
    good luck
    HTH

  • Creating RMA Order through OE Interface Tables

    Hi,
    We are needing the ability to create RMA orders using the OE interface tables but we are running into an issue. The SOURCE_DOCUMENT_ID that is populated in Oracle Apps to link the RMA back to the original order does not get populated and there is no source_document_id column in the interface tables to populate manually. Does anyone know how we can get the SOURCE_DOCUMENT_ID populated for RMAs?
    Thanks in advance for your assistance,
    Troy

    Hi Nagamohan,
    I entered the reference_type, reference_header_id and the reference_line_id in the OE_LINES_IFACE_ALL (and a record in the headers iface, of course) and ran the Order Import. I set the reference_type to 'ORDER' but it didn't populate that on the new line record in oe_order_lines_all. And the source_document_id still is not populated. It did populate the referehcen_header_id and reference_line_id on the line, but we don't use those fields. We use the 'source' fields.
    I also noticed that the source_document_type_id is populated on RMA order headers and lines that are copied and created in Oracle Apps but there is no place to pass this column to the interface. Do you know how this value and the source_document_id and source_document_line_id can be populated when creating the RMA through the interface?
    Thanks
    Troy

  • I downloaded an album on itunes using my new itouch; but it's only allowing me to put three songs at any one time into the music app...how can i get it to just move them all in there?

    i downloaded an album on itunes using my new itouch; but it's only allowing me to put three songs at any one time into the music app...how can i get it to just move them all in there?

    hi philly, thanks for getting back to me, especially on such a busy day.
    I don't think that's quite the issue though. I bought an album and it appears in 'my purchases' within the itunes app. Yet, in order to listen to the music, i must use the 'music' app and in this application, there are only three tracks displayed at any one time from my downloaded album.
    I can 'download all' from the 'my purchases' section but that still doesn't help, it just keeps the last three tracks downloaded in the music app.
    I have the 'icloud' enabled and wondered if it had anything to do with that.
    i have successfully downloaded another full album totally into the music app, but this first album is causing me problems.

  • I wonder how pro photographers use aperture?I shoot raw and my harddrive is alreay full.I'm not able to import new pictures.Is it ok if i create a vault and delete all my projects in the HD.Can I use an external HD use aperture through the vault??

    I wonder how pro photographers use aperture?I shoot raw and my harddrive is alreay full.I'm not able to import new pictures. I don't know what to do. I created a vault. My plan was to create a vault(put all my master files into an external harddrive) and then delete all my projects in my mac pro's harddrive. Is it the correct way to do it ? What should I do if I have thousands of raw files ? How should my workflow be? Can I use an external HD and use aperture through the vault,without keeping the master files on my computer's hard drive?? Or should I shoot raw+jpeg and store raw files in an external backup harddrive and import only jpegs into my aperture library?

    There's a bit to learn.  It will slowly make sense.
    Aperture is an empty field.  You're given a tractor and a whole bunch of attachments. What you grow, how, and where, is entirely up to you.
    Vaults are for back-up and only for back-up.  They have nothing to do with storing your working files.
    When your Library outgrows your system drive (and for good performance, you should leave c. 20% of every drive empty), it's time to convert some of your image's Masters from Managed to Referenced.  ("Managed" and "Referenced" refer to Masters, not to Libraries.)
    There are hundreds of posts in the forum, and several pages in the User Manual on using Masters.
    Many people run Aperture with the Library on their system disk, and most (or all) of their images' Masters on external FW drives.  This is a good set-up.  Note that you will likely have to take steps to back-up the data on your external drives.
    If you do the above, there should be no reason to delete any Projects.
    The choice of RAW or RAW+JPEG or JPEG depends on the kind of work you are doing.  I capture RAW only -- but I don't do any commercial shoots.  Pros on deadlines report that the RAW+JPEG works well for them.  Capture JPEG if it saves you time.  IMHO, there is not a good reason to shoot JPEG to save space (space is cheap; time expensive).
    Short-term solution: buy and use a FW800 external 1 TB drive, formatted "Mac OS Extended (Journaled)", and using Aperture relocate the Masters of all images older than 30 days to that drive.  (Be sure to change your back-up strategy to include this new drive; you may need a second new drive.)
    This general post of mine might help you understand more about Aperture.

Maybe you are looking for