[JS CS3, Win] Saving InDesign using app.activeDocument.save

Hello.
I am having problems saving an InDesign document using Javascript.
My aim is to have a box in the document where I will type the filename and path where I want the InDesign file to be saved (eventually this will be generated from a datamerge).
I then want to run a script which will read the contents of the box and then save the document to that filename or location.
At the moment I have:
//SaveText.jsx
//An InDesign CS3 JavaScript
//Saves the document to the provided path
//get contents of the FileNameBox box on the document
var varFileName = app.activeDocument.textFrames.item("FileNameBox").contents;
//now save
app.activeDocument.save("/"+ varFileName+".indd");
//alert (app.activeDocument.filePath);
When I run the script (with "Hello" in the FileNameBox) the file changes name on the top bar of InDesign to "Hello.indd", but (when I run the commented out alert at the end) the file is not actually saving anywhere.
If I close InDesign and then open it the file is listed under "Open Recent" on the menu, but clicking it does nothing - again the file doesn't exist.
Does anyone have any ideas to help me from tearing my hair out?
Where is my file saving? (Or, if it isn't, how can I make it save!).
Thanks in advance for any help you can offer.

var myFolder = new Folder("~/Desktop/Test");
if (!myFolder.exist) myFolder.create();
var varFileName = app.activeDocument.textFrames.item("FileNameBox").contents;
app.activeDocument.save(myFolder.fsName + "\\" + varFileName+".indd");
alert(app.activeDocument.filePath);

Similar Messages

  • Query on app.activeDocument.exportFile

    (Apologies if this is an Illustrator scripting question rather than a CEP specific extension one)
    From Adobe Illustrator CC2014 HTML5 extension I am using app.activeDocument.exportFile to export the activeDocument to SVG.
    I have that working great but what happens is that the exported file becomes the active document (replacing the .AI document that was open) and I do not want this to happen?
    Can anyone explain this behavior and how I could change it.

    I got around it by closing new doc and reopening
        app.activeDocument.save();
        var srcFile = app.activeDocument.fullName;
        app.activeDocument.exportFile( fileSpec, type, exportOptions );
        app.activeDocument.close(SaveOptions.SAVECHANGES);
        app.open(srcFile);

  • InDesign CC won't save my files

    Hi
    I've been working in InDesign for a week now and since yesterday I started noticing that at times InDesign won't undo and I am not able to save my file. I keep hitting command + s while working but it just doesn't save or give an error message. If I go on the File menu all the save and save as commands are grayed out. If you close the file and click on the save button InDesign just gives a message that the file cannot be saved. I have to close the file without saving and redo all the work. Because InDesign doesn't give an error when pressing command + s I would do a lot of work under the impression everything gets saved but it doesn't and I keep losing a lot of work.
    Also CC runs very slow. There are times when the program just "freezes" for awhile while InDesign does somethings in the background and only after it is done you can start working again. The pages panel takes ages to load the previews onto the pages and while it is doing so I cannot do anything at all.
    Starting to think I should have stayed with CS6.

    @all – the above JavaScript (ExtendScript) in post #34 cannot work as expected on Mac OSX.
    At best you will save a file named "Test\test.indd" on the desktop…
    Instead I would recommend a slightly altered version:
    var myFolder = new Folder("~/Desktop/Test");
    if (!myFolder.exist) myFolder.create();
    app.activeDocument.save(myFolder.fsName + "/" +Date.now()+"_test.indd");
    See the "/" instead of "\\".
    I changed it, so every time you execute it (and if it will not throw an error!), you'll get a new file with an unique file name.
    ("Date.now()" should be sufficient enough to generate a new sequence of a 13 digit number every time you try).
    Or maybe even better: save a copy of your file:
    var myFolder = new Folder("~/Desktop/Test");
    if (!myFolder.exist) myFolder.create();
    app.activeDocument.saveACopy(myFolder.fsName + "/" +Date.now()+"_test.indd");
    All testing on Mac OS X 10.6.8.
    @BienzBliemer – I think, the above script(s) will not work in your scenario, because InDesign has not finished something that goes on in the background. A hidden modal dialog that is not answered should not be the problem, because you can start up a script …
    Uwe

  • How do I write a javascript code to open InDesign File, import Doc, save and export to pdf?

    How do I write a javascript code to open InDesign File, import Doc, save and export to pdf?

    Hi hasvi,
    Need Template(.indt), textframes etc for the following script:
    var myFolderInd = Folder.selectDialog();
    var myFile = myFolderInd.getFiles("*indt");
    app.open(myFile)
    var myDoc = app.activeDocument;
    var myDocName = myDoc.name;
    var mySaveFile = app.activeDocument.save(myFolderInd.fsName + "/" + myDocName.split(".indt").join(".indd"));
    var myFolderDoc = Folder.selectDialog();
    var myFile1 = myFolderDoc.getFiles("*doc");
    mySaveFile.pages[0].textFrames[0].place(File(myFile1))
    //~ mySaveFile.place(File(myFile1))
    app.activeDocument.textPreferences.smartTextReflow = true;
    var myPDFFile = new File(mySaveFile.filePath + "/" + mySaveFile.name.split(".indd").join(".pdf"))
    myDoc.exportFile(ExportFormat.PDF_TYPE, File("~/Desktop/abc.pdf"));
    alert("Process Completed")
    Regards
    Siraj

  • "activeDocument.saveAs" does not work! -- Error 8800 | PS CS5 | Mac OSX 10.5.8

    Error 8800: General Photoshop error occurred. This functionality may not be available in this version of Photoshop.
    I even tried to copy the Script from the scripting Guide.
    jpgFile = new File( "/Temp001.jpeg" )
    jpgSaveOptions = new JPEGSaveOptions()
    jpgSaveOptions.embedColorProfile = true
    jpgSaveOptions.formatOptions = FormatOptions.STANDARDBASELINE
    jpgSaveOptions.matte = MatteType.NONE
    jpgSaveOptions.quality = 1
    app.activeDocument.saveAs(jpgFile, jpgSaveOptions, true,
    Extension.LOWERCASE)
    Everything else in my Scripts work :-/
    Any Tipps?

    The reason the original script did not work is new File( "/Temp001.jpeg" ) is not a valid file path. The path must be the full URL not a releative one.
    The reason the second script saves to the folder where Photoshop is installed is because path is a reserved word in Photoshop. Even is you assign something else to path like var path = app.activeDocument.path, it will still point to the app path. name is another reserved word. It will always return 'Adove Photoshop'.
    Better to do something like this.
    var docPath = app.activeDocument.path;
    var jpgFile = new File( docPath + "/Temp001.jpeg" );

  • App.executeMenuItem("SaveAs")

    I have a Reader Extended PDF form and I am trying to script a button to use the SaveAs method. Is it possible to specify a default filename using app.executeMenuItem("SaveAs")? By default, it uses the PDF form name.
    If it is possible, is there any way to suppress the Save As dialog from appearing?

    It should work but the form must be Reader EXtended or opened in Acrobad.

  • Changes lost after saving InDesign CS3 (WIN)

    Part of our work is to make amendments to books we've typeset in InDesign. As is normal practice, we save and check our work as we go along, and subsequently close the indd file. On a few occasions now, when we have re-opened a file, we have found some of the changes we've made have not been kept. These seem to happen at random through a book, and it has happened rarely enough to prevent us getting to the bottom of it (are we doing something wrong in haste, etc?). For instance, we thought it could be our inadvertently causing Undo to do more than one edit, but our investigations on the latest occurrence of this have convincingly ruled this out. The working files are stored on the computer's hard drive (before being backed up to our server), so it's not a qestion of problems saving directly to a server, either. (So far we haven't experienced this problem on our Mac.)
    We are now wondering if InDesign's ability to keep track of every save (version) of a document, which I understand is accessible through Version Cue (which we don't have installed) is at the heart of the problem. Could InDesign be retrieving earlier save-versions of a file each time we save?
    Anybody any idea what could be going on? More to the point: how can we prevent this happening without our having to check again (and possibly repeatedly) through what can sometimes be more than a hundred author's amendments?
    Ideas would be gratefully received.
    Rob Fris
    documen

    In a message dated 29/03/2010 23:25:17 GMT Daylight Time, [email protected] 
    writes:
    http://forums.adobe.com/message/2698024#2698024
    Many thanks for this. As a result we have adjusted our way of working in 
    InDesign to use Save As and overwrite rather than use Save.
    Rob

  • Saving Indesign CS3 to Indesign CS

    Does anyone know how I can save an Indesign file from CS3 so that Indesign CS (the one with the brown butterfly icon) can open it?
    Is it possible?
    And can I then open it up again in CS3 after making changes in CS??
    Many thanks!
    Stu

    Export as INX. Open that in CS2 and do the same thing. Open that in CS.
    Be prepared to find a dramatically different document depending upon
    what features you used in CS3.
    This is not a recommended workflow!
    Bob

  • App.activeDocument.cropBox returning an error (CS3)

    Hi friends
    My script currently being developed is working perfectly in Illustrator CS5, CS6 and CC. When testing in Illustrator CS3, the line where I read the cropBox property of the activeDocument returns an error. So I tried to isolate this property in order to test it. So here's my test:
    var doc = app.activeDocument;
    var v = doc.cropBox;
    Even running from Extended Script or directlly in Illustrator (and even declaring #target illustrator and #targetengine main) the line about cropBox stops and gets the error. Debugging in ESTK it returns the error:
    "The property was not initialized"
    Am I missing anything?
    In newer Illustrator versions it works fine. But in CS3 not.
    Thank you very much for the help
    Gustavo

    Hi pixxxel
    Thank you very much for testing.
    Strange. Here, in my test machine (Windows 7 64 bits), I´m not able to read this property! It returns that error.
    Well..anyway I found and alternative reading the width and height and rulerOrigin of the document. But the cropBox is really not reading haha!
    Best Regards and thank you very much
    Gustavo

  • Can you open/edit indesign files on CS3 that were created using CS5?

    I recently bought indesign CS5 and am using this for my internship; however, my boss is still using CS3 and said she could not open or edit the indesign file i sent her.  I looked under "export" to see if there was an option and did not find anything.  I am using a mac and I believe she is using a P.C., also, when I last sent her the file, I was still using my free trial - does any of this make a difference?  Please help! 

    This has been covered endless times but anyway, I'll do it again!
    You have to export an idml file from CS5, then open that idml in CS4, export an inx file from there then open that in CS3 and save as an indd.  Sorry but there is no way round it, fullstop, end of story etc etc.  So if she is using CS3 and you're using CS5 there is no route between them unless you have CS4, and even then the route is littered with pitfalls!  Look here for a rather long discussion / sometimes rant on the subject.
    Ultimately she'd have to upgrade, or you could see if you could buy a CS3 or 4 version but it is very hard to get a legitimate copy, the only way is buy it off someone you know and most people aren't selling because they're upgrading.
    Best news last, there is a short term fix, go to this guys blog and you can download a trial version of CS4 which will last for a month.

  • CS6 Indesign on App-V 5 using Xenapp 6.5 provisioned servers.

    Hi
    We are trying to deploy Indesign CS6 using App-V 5 on provisioned Xenapp 6.5 servers. I have tried different solutions without any luck.
    Making an install packet using AAMEE 3.1. Sequencing packet in App-V.  According to the AAMEE manual this would remove the “machine dependency” in the packet and serializing it.
    Using this solution we are able to start Indesign once on every server. The next time we try to start it  crashes. We can see it starts up adobe_licutil.exe just before chashing.
    We have also tried using adobe_prtk.exe to serialize the installation using prov.xml without any luck.
    Can anyone point us in the right direction? AAMEE or Trial with adobe_prtk.exe, a combination or something else?
    Best regards
    Morten

    Hi msn9000aa,
    Sorry again for the confusion. I thought you were trying to deploy CS4. For CS6 please refer the CS6 deployment guide: http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/Ad obeApplicationManagerEnterpriseEditionDeploymentGuide_v_3_1.pdf.
    There are two ways we can serialize a file:
    1. Using AAMEE 3.1 and creating a serialize file and running it on the machine to license the software. Detailed information is mentioned in the guide above.
    2. Using APTEE for serialization. Please refer the kb:  http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/Ad obe_Provisioning_Toolkit_Enterprise_Edition_v5.pdf.
    However as mentioned in my earlier thread please refer the kb: http://helpx.adobe.com/creative-suite/kb/technical-support-boundaries- virtualized-or.html for suppot boundries related to virtualized enviroment.
    Regards,
    Romit Sinha

  • Possible bug in Photoshop CS6 with app.activeDocument.path.

    JavaScript running in Photoshop CS6 under OS X 10.7.5 returns the wrong result for app.activeDocument.path when the file is located on the boot drive. The result is undefined and an error message incorrectly states that the document has not been saved yet. If the file is located on a remote volume, the correct path is returned.
    To reproduce this problem, create a new file in Photoshop CS6 on a Mac. Save the file to the desktop. With the file still open, run the following script in ExtendScript Toolkit.
    // start script
    var thePath = app.activeDocument.path;
    alert(thePath);
    // end script
    Running the same script with a file located on a server volume open in Photoshop correctly returns "/path/to/file.psd" instead of undefined and no error occurs.
    This appears to be a bug in Photoshop CS6's JavaScript implementation. This problem did not exist in Photoshop CS3.
    A similar issue prevents Photoshop CS6 from saving files to the boot drive using activeDocument.saveAs.
    Has anyone else experienced this problem? If so, have you discovered an alternate method to determine the file path or save a file on the boot drive?

    Don't know if this will help much but at least you can use it to check a document's filepath without throwing an error. And maybe tell if the problem is with the Photoshop DOM.
    function hasFilePath(){// returns true/false
        var ref = new ActionReference();
        ref.putEnumerated( charIDToTypeID("Dcmn"), charIDToTypeID("Ordn"), charIDToTypeID("Trgt") );
        return executeActionGet(ref).hasKey(stringIDToTypeID('fileReference'));
    function getFilePath(){// returns path as a string if exists, undefined if not
        var ref = new ActionReference();
        ref.putEnumerated( charIDToTypeID("Dcmn"), charIDToTypeID("Ordn"), charIDToTypeID("Trgt") );
        var desc = executeActionGet(ref);
        if(desc.hasKey(stringIDToTypeID('fileReference'))) return decodeURI(desc.getPath(stringIDToTypeID('fileReference')));

  • App.activeDocument no longer works right

    In a different topic, I was explaining my use of app.documents[0] rather than app.activeDocument. I was going to elaborate some about the differences when I hit a snag. There was a dramatic change after CS3 and apparently nobody noticed. I didn't until today. Look at this simple script that expects there to be more than one document open:
    docZero = app.documents[0];
    activeDoc = app.activeDocument;
    $.writeln("docZero: " + docZero.name);
    $.writeln("activeDoc: " + activeDoc.name);
    // move back document to front
    app.activeDocument = app.documents[-1];
    $.writeln("\ndocZero: " + docZero.name);
    $.writeln("activeDoc: " + activeDoc.name + "\n");
    $.writeln("docZero: "+ docZero.toSpecifier());
    $.writeln("activeDoc: " + activeDoc.toSpecifier() + "\n");
    In CC, I was astonished to discover that I got this result (after creating two untitled documents):
    docZero: Untitled-2
    activeDoc: Untitled-2
    docZero: Untitled-2
    activeDoc: Untitled-2
    docZero: /document[0]
    activeDoc: /document[@id=2]
    That second docZero ought to say Untitled-1. Untitled-1 was definitely moved to the front by the app.activeDocument = app.documents[-1] statement. So looking at the docZero specifier, how come I got the wrong name?
    I decided to check my sanity and went back to see what happens in CS3 -- the oldest InDesign I still have installed (actually, on two different computers, so I tried it on both). CS3 gives:
    docZero: Untitled-2
    activeDoc: Untitled-2
    docZero: Untitled-1
    activeDoc: Untitled-2
    docZero: /document[0]
    activeDoc: /document[@name="Untitled-2"]
    There's two interesting things here:
    The second docZero message has the correct name of the document that was moved to the front.
    In those days, documents were identified by name, not id.
    Point 2 is interesting but off topic.
    So I tried CS4 (also on two machines). It gave:
    docZero: Untitled-2
    activeDoc: Untitled-2
    docZero: Untitled-2
    activeDoc: Untitled-2
    docZero: /document[0]
    activeDoc: /document[@name="Untitled-2"]
    So this is when things started to go wrong. Interestingly, documents were still identified by name in CS4, so it wasn't that change that caused the change in behavior. It was CS5 (which produced exactly the same output as CC) where the specifier changed to using the id -- a property that had not previously existed for Document objects.
    So, I guess the question is: Is this a bug? Looks like one to me. Looks like it stopped working after CS3.
    Dave
    Message was edited by: DaveSofTypefi -- minor formatting change

    Hi Dave,
    This is a typical specifier resolution problem, and indeed this is not related to id-based document specifiers introduced in CS5.
    How specifiers are resolved is consistant since CS4—except for Text and Cell specifiers, but this another story.
    Here is what happens:
    Unlike activeDoc = app.activeDocument (which is instantly resolved), docZero = app.documents[0] remains an unresolved specifier until you hit some property on it, which is done at the next line, when you innocently display the name property:
    $.writeln("docZero: " + docZero.name); // this code sends a command that resolves docZero
    Then, whatever you do, docZero is internally resolved to an actual receiver (the Untitled2 document), even if the specifier string accessed from docZero.toSpecifier() still contains the original path "/document[0]". Ironically, if you didn't prompt docZero.name before sending the command app.activeDocument = app.documents[-1]; then docZero would have been properly resolved to the Untitled1 document! Remove the first $.writeln and you will see the change.
    Now, the question is: how to force a new resolution of the specifier considering its formal path "/document[0]". The answer is getElements(). Just access this method and the magic happens:
    docZero = app.documents[0];
    alert("docZero: " + docZero.name);          // => Untitled-2
    // move back document to front
    app.activeDocument = app.documents[-1];
    docZero.getElements();                      // resolve again!
    alert("\ndocZero: " + docZero.name);        //  => Untitled1
    alert("docZero: "+ docZero.toSpecifier());  // still /document[0]
    See also: http://www.indiscripts.com/post/2010/07/on-everyitem-part-2
    @+
    Marc

  • [JS CS3 Win] Export to PDF then auto-print PDF from Acrobat

    Hello!
    I am working on the script that is exporting pages to PDF, and would like to automatically send exported PDF to print from Acrobat.
    I get the scripting part for exporting to PDF, and it's working very well, but I have trouble on the part of the script that tells Acrobat to open the PDF and send it to printer. Script is run from InDesign, so I thought this is right forum to ask.
    The following part of the script is working OK on one computer, but on other two computers with similar configuration (CS3. Windows, Acrobat 8) it doesn't work at all and I can't figure out where is the problem:
    var printFile = "/c/temp/test.pdf";
    var remoteScript = "printFile = decodeURI('"+printFile+"');\n";
    remoteScript += "var doc = app.openDoc({cPath: printFile});\n";
    remoteScript += "var pp = doc.getPrintParams();\n";
    remoteScript += "pp.pageHandling = pp.constants.handling.shrink;\n";
    remoteScript += "pp.NumCopies = 2;\n";
    remoteScript += "pp.interactive = pp.constants.interactionLevel.silent;\n";
    remoteScript += "pp.printerName = '\\\\hrhqzgw23prn01\\\hr300019ps';\n";
    remoteScript += "doc.print(pp);\n";
    remoteScript += "doc.closeDoc(true);";
    acrobat.executeScript(remoteScript);
    I would appreciate any help. thank you.

    Hi Mark,
    Here is a sample script. It exports the active InDesign document to pdf file, using its base name, to the root of C drive. Then opens the exported file in Acrobat, prints it to the default printer and silently closes it.
    Tested on InDesign 5.0.3, Acrobat 8.0.0, Windows XP SP3.
    #target indesign
    var myIndesignDoc = app.activeDocument;
    var myBaseName = GetFileNameOnly(myIndesignDoc.name);
    var myFile = new File( "/C/" + myBaseName + ".pdf" );
    myIndesignDoc.exportFile( ExportFormat.pdfType, myFile, false );
    var myScript = 'var myAcrobatDoc = app.openDoc( "/C/' + myBaseName + '.pdf" );\n';
    myScript += 'myAcrobatDoc.print( {bUI: false, bSilent: true} );\n';
    myScript += 'myAcrobatDoc.closeDoc( true );';
    var bt = new BridgeTalk;
    bt.target = "acrobat";
    bt.body = myScript;
    bt.send();
    function GetFileNameOnly(myFileName) {
        var myString = "";
        var myResult = myFileName.lastIndexOf(".");
        if (myResult == -1) {
            myString = myFileName;
        else {
            myString = myFileName.substr(0, myResult);
        return myString;
    Short explanation of the acrobat script:
    1. Open the pdf file, just exported from InDesign
    var myAcrobatDoc = app.openDoc( "/C/' + myBaseName + '.pdf" );
    2. To print the document silently I use the doc object’s print method and set the following parameters:
    bUI -- Determines whether to present a user interface to the user
    bSilent -- Suppresses the Cancel dialog box while the document is printed
    myAcrobatDoc.print( {bUI: false, bSilent: true} );
    3. Close the document without notifying the user:
    myAcrobatDoc.closeDoc( true );
    Regards,
    Kasyan

  • [JS CS3 WIN] ExportEachPageAsPDF

    Hello,
    I have found this script. Now I want to modify the filename section.
    //ExportEachPageAsPDF.js  
    //Exports each page of an InDesign CS document as a separate PDF to  
    //a selected folder using the selected PDF export settings.  
    //Display a "choose folder" dialog box.  
    if(app.documents.length != 0){  
        var myFolder = Folder.selectDialog ("Choose a Folder");  
        if(myFolder != null){  
            myExportPages(myFolder);  
    else{  
        alert("Please open a document and try again.");  
    function myExportPages(myFolder){  
        var myPageName, myFilePath, myFile;  
        var myDocument = app.activeDocument;  
        var myDocumentName = myDocument.name;  
        var myPDFPresets = app.pdfExportPresets;
        var myPDFPresetNames = new Array;
        for (i = 0; i < myPDFPresets.length; i++)
            myPDFPresetNames.push(myPDFPresets[i].name); 
        var myDialog = app.dialogs.add();  
        with(myDialog.dialogColumns.add()){ 
            with(dialogRows.add()){   
                with(dialogColumns.add()) {
                    staticTexts.add({staticLabel:"Base name:", minWidth:130});  
                with(dialogColumns.add()) {
                    var myBaseNameField = textEditboxes.add({editContents:myDocumentName,   minWidth:160});  
            with(dialogRows.add()){ 
                with(dialogColumns.add()){ 
                    staticTexts.add({staticLabel:"PDF preset: ", minWidth:130}); 
                with(dialogColumns.add()){ 
                    var myPDFPresetsDropdown = dropdowns.add({stringList:myPDFPresetNames,  selectedIndex:0}); 
        var myResult = myDialog.show({name:"ExportPages"});  
        if(myResult == true){  
            var myBaseName = myBaseNameField.editContents;  
            var myPDFPresetName = myPDFPresetNames[myPDFPresetsDropdown.selectedIndex];
            //Remove the dialog box from memory.  
            myDialog.destroy();  
            for(var myCounter = 0; myCounter < myDocument.pages.length; myCounter++){  
                myPageName = myDocument.pages.item(myCounter).name;  
                app.pdfExportPreferences.pageRange = myPageName; 
    //Generate a filename. /////////////////////////////
              app.findTextPreferences.appliedParagraphStyle = "picture_description"; 
              app.findTextPreferences.findWhat = '';
             myStory = myDocument.stories;
              myFound = myStory.findText();
           // alert(myFinds[0].contents);
                myFilePath = myFolder + "/" + myFound[0].contents + ".pdf";  
                myFile = new File(myFilePath);  
                myDocument.exportFile(ExportFormat.pdfType,   myFile, false, myPDFPresets.item(myPDFPresetName)); 
        else{  
            myDialog.destroy();  
    On every page there is only 1 paragraph styled with the paragraphstyle "picture_description".
    I want to use the content of this paragraph for the filename for each page.
    please, can someone help me?
    Best regards
    Christoph

    Hi Christoph,
    Here's a script for you:
    http://www.nobrainer.dk/assets/Uploads/Scripts/share/exportPDFofPage-nameByParaStyle.jsx
    You should notice that there is no looking out for errors and other fancy stuff, so your document must have one line marked with the parastyle "picture_description", on each page that should be exported. Also there can be no illigal letters for a filename in the marked text.
    However you should easily be able to make corrections to the script as needed.
    Thomas B. Nielsen
    http://www.nobrainer.dk

Maybe you are looking for

  • File from the Application server

    Hi gurus, I am working on a scenario where I need to get a file from the application server and for this I need to ask user to enter the location and that too at the selection screen and then I need to read this location using open data set and read

  • Hp slate 7 voice tab, kitkat update

    I have this problem with my hp slate 7 voice tab. When I installed the kitkat update, my tablet kept on rebooting and then it stops and shows options or ways I could fix the issue. I tried every single option and it still does not work. I have been w

  • Inserting summary value in a ZTABLE

    Hi Experts, Please guide me on how the following: I have created a Ztable into which i want to upload the Stock in a summary format i.e. i have got the above values in an internal table. now i want to insert the sum of results into another internal t

  • WebUtil and 9i db

    Hi, What features of the 9i database are used by WebUtil? I am on 8i (8.1.7.4) and was wondering if it was absolutely necessary to be at 9i. Thanks, Mitch

  • How can I create a camera profile in LR4 from my camera

    I have a 5d mark 2, and I created a custom camera profile that is ideal for me, however when I shoot raw it only gives me the adobe, and camera standards etc. Is there a way that I can take my user setting on my 5d and transfer it into lightroom??