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

Error in calling a MS Word macro from A5 script

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

  • Error in calling a MS Word macro from A5 script

    I'm developing a document control application. Documents are written with MS Word. Stamping the document control number (DCN) into the Word document footer is a central need. I am placing the DCN onto the clipboard (clipboard_set_data()), opening Word and trying to run a Word macro that pastes the clipboard content into the document footer. The first time it attempts this, it generates the OLE error in the attached screenshot, and leaves WINWORD.EXE as an open windows process. Deleting the WINWORD.EXE from Windows task manager clears this, and from then on, the script runs without errors. Close A5 app, reopen the app and try it again, first time failure, clear the residual WINWORD.EXE from task manager and from then it works OK. What do I need to do to get this to work the first and every time? I've tried pausing things between the commands with xbasic_wait_for_idle(), sleep(), etc, with no joy. I need help, please.

    Code:
    ' generate the file address
    	dim vdoc_file as C
    	vdoc_file=alltrim(vg_doc_template_path)+"test.doc"
    
    ' generate the footer and attach to the clipboard
    	dim shared vfooter_text as C
    	vfooter_text="This is footer text for the document for testing"
    	:clipboard.set_data(vfooter_text)
    
    ' place the Word macro name (doc_footer_stamp) into a variable
    	dim vword_macro as C="doc_footer_stamp"
    
    ' open the word application hidden (windowstate=0) calling the document by the above variable 
    	on error goto error_handler
     
    	Dim wordApp As p	
    	wordApp = ole.Create("Word.Application")
    	wordApp.WindowState = 0 
    	wordApp.Documents.Open(vdoc_file)
    	
    ' stamp document info into footer	
    	wordApp.run(vword_macro)                             [COLOR="Red"]<<< error spot[/COLOR]
    	wordApp.ActiveDocument.SaveAs(vdoc_file)
    	wordApp.quit()
    	GOTO TERMINAL
    
    'error handler
    	error_handler:
    	dim vstamp_error as C
       	err = error_code_get()
                 vstamp_error= error_text_get(err)
       	
                 ON ERROR RESUME 0
                 msgbox("Error Report",vstamp_error)
                 end
    
    TERMINAL:
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

  • #2
    Re: Error in calling a MS Word macro from A5 script

    Hi Mike,
    If a solution does not come your way, there is a way to kill the service via xbasic and a batch file easily that could be run as part of your script--if memory serves, even if the process is not running, no error will be generated when run so should work as a work-around if needed.

    I have an example on a different computer if this will be what is required....
    Mike
    __________________________________________
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau
    __________________________________________



    Comment


    • #3
      Re: Error in calling a MS Word macro from A5 script

      Thanks Mike,
      At this point, I'm up for any solution.
      Mike W
      __________________________
      "I rebel in at least small things to express to the world that I have not completely surrendered"

      Comment


      • #4
        Re: Error in calling a MS Word macro from A5 script

        Try changing

        wordApp = ole.Create("Word.Application")

        to

        wordApp = ole.GetObject("Word.Basic")
        There can be only one.

        Comment


        • #5
          Re: Error in calling a MS Word macro from A5 script

          Thanks Stan but no joy there.
          Mike W
          __________________________
          "I rebel in at least small things to express to the world that I have not completely surrendered"

          Comment


          • #6
            Re: Error in calling a MS Word macro from A5 script

            I think the documentation is lacking.

            Should be


            wordApp = ole.getobject("","Word.Application")
            There can be only one.

            Comment


            • #7
              Re: Error in calling a MS Word macro from A5 script

              OUTSTANDING!!!!!! I can't thank you enough Stan! I'm headed to the AlphaWiki and see if that needs to be changed in the Docs.
              Mike W
              __________________________
              "I rebel in at least small things to express to the world that I have not completely surrendered"

              Comment


              • #8
                Re: Error in calling a MS Word macro from A5 script

                Much better to cure the problem instead of creating a work-around for sure! Glad I did not come back until now with the work-around.

                For others in case it is needed for similar or other things here is what I planned on giving Mike as a way to close the process via code.

                Very simply create a batch file (a text with a .bat instead of a .txt extension) with the following using the appropriate program name.exe. Also note that this will only work if a user has a password set up for log in. Run the Bat file with sys_shell_wait() from Alpha.
                Code:
                @echo off
                TASKKILL /F /IM YourProgramNameInTaskManager.exe
                Mike
                __________________________________________
                It is only when we forget all our learning that we begin to know.
                It's not what you look at that matters, it's what you see.
                Henry David Thoreau
                __________________________________________



                Comment

                Working...
                X