Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Ole call hangs up

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Ole call hangs up

    I searched this and found this but didn't find an answer.
    http://msgboard.alphasoftware.com/al...light=ole+call
    I found the threads that allowed me to learn this, but not help with this problem.

    I have the following script which opens a Word document, fires a Word macro and closes. It works well AFTER the first run. The very first run can take minutes to execute with a couple of warning messages about "the ole method call is taking longer than expected. D you want to continue waiting?". I will eventually, after several minutes complete. BUT, after the first connection, it works fine. On my stand alone dev computer it takes 1-2 minute. On my networked computers 3-5 minutes. Does anyone know what causes this and how I might get around this extrodinarily long wait for the first call? Thanks


    Code:
    '> docname created elsewhere
    dim shared vstamp_error as C
    on error goto error_handler1
    dim vmacro1 as C="doc_sign_stamp"
    Dim wordApp As p
    wordApp = ole.getobject("","Word.Application")
    'wordApp = ole.Create("Word.Application")		‘ doesn’t seem to work with this
    wordApp.WindowState = 2   'wdWindowStateMinimize
    wordApp.Documents.Open(docname)
    end
    
    error_handler1:
    dim shared vstamp_error as C
    vproceed="no"
    err = error_code_get()
    vstamp_error= error_text_get(err)
    if "Microsoft Word" $ sys_id_enum()
         wordApp.quit()
    end if
    
    ON ERROR RESUME 0
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    #2
    Re: Ole call hangs up

    I don't see where you're closing the ole unless there is an error. I don't see where the document is saved after the macro runs, assuming the macro changes something.

    See if this helps.

    Code:
    '> docname created elsewhere
    dim shared vstamp_error as C
    on error goto error_handler1
    dim vmacro1 as C="doc_sign_stamp"
    Dim wordApp As p
    wordApp = ole.getobject("","Word.Application")
    wordApp.WindowState = 2   'wdWindowStateMinimize
    wordApp.Documents.Open(docname)
    wordApp.DisplayAlerts = .F.
    'I assume the macro runs when the document is opened?
    wordApp.ActiveDocument.Saveas(docname)
    wordApp.DisplayAlerts = .T.
    wordApp.Quit()
    delete wordApp
    end
    
    error_handler1:
    dim shared vstamp_error as C
    vproceed="no"
    err = error_code_get()
    vstamp_error= error_text_get(err)
    if "Microsoft Word" $ sys_id_enum()
         wordApp.quit()
    end if
    
    ON ERROR RESUME 0
    There can be only one.

    Comment


      #3
      Re: Ole call hangs up

      Hi Stan,
      Thanks for replying. The code I posted is a portion of a longer script that loops through many records, calls a word document, stamps a line in the document footer through a Word macro, and saves the document. After the application is first opened, when the script executes, the very first ole call takes many minutes. With patience and after several dialogs reporting that "the process is taking longer than expected, continue?", it eventually completes the first loop, then after that, it flows quickly. It's that first Ole call that takes like forever. I am not knowledgeable enough to know what Ole is, so I can't even troubleshoot this.

      I placed the code lines you provided me into my script. The wordApp.DisplayAlerts = .T. generated an error. I have tried all this using Word 97, 2000, and 2003, and tried using the window state 0, 1 and 2, and all combos seem to have a terrible time with that very first Ole call. I've got to believe there is some trick to bypass this.
      Mike W
      __________________________
      "I rebel in at least small things to express to the world that I have not completely surrendered"

      Comment

      Working...
      X