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



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

How to find path to MS Word for use with SYS_Shell

  • Filter
  • Time
  • Show
Clear All
new posts

    How to find path to MS Word for use with SYS_Shell

    How can I find the path to MS Word on a local machine? Word may be installed in a different location on different machines.

    I need to use sys_shell to open a Word document. I need to use sys_shell instead of sys_open because I need to control the Window Mode.

    Thank you in advance for help,


    Re: How to find path to MS Word for use with SYS_Shell

    ? filefind.get_recurse("C:\\","winword.exe")
    = C:\Program Files\Microsoft Office\OFFICE11\WINWORD.EXE
    If you can rely on the executable being in the C:\program files\microsoft office directory this will be much quicker.

    filefind.get_recurse("C:\Program Files\Microsoft Office\\","winword.exe")
    If you must use the first version I would suggest you do it when the startup form loads and store it in a global variable to reference elsewhere rather than finding it multiple times.
    Last edited by Stan Mathews; 06-17-2011, 11:33 AM.
    There can be only one.


      Re: How to find path to MS Word for use with SYS_Shell

      This is what I eventually came to in order to open a specific word file on any computer with Word 2000 with much help from others. If you search my name and "Word", you will find Marcel, Stan's and others helping me through this. Make specific to your app what is in red. I imagine there is a way to adjust the mode, try playing with what I have in blue. Some number might be minimized, etc. This also works with Word 2003. I have no experience with higher versions of Word.

      ' get pointer to the table
      	dim tm as p
      ' generate the document name for the current record and folder path
      	dim vdoc_folder_path as C="[COLOR="red"]C:\databases\document_control"+chr(92)[/COLOR]
      	dim docname as C
      	'set the signature for the document for the Word macro "doc_sign_stamp" to place
      	dim shared vsign_stamp_text as C="JMW"
      	' asssure the record is NOT IN READ ONLY CONDITION 
      ' open the word application calling the document by the above variable 
      	on error goto error_handler
      	dim vmacro1 as C="[COLOR="red"]doc_sign_stamp[/COLOR]"
      	dim vmacro2 as C="[COLOR="red"]doc_footer_stamp[/COLOR]"
      	Dim wordApp As p
      	wordApp = ole.getobject("","Word.Application")
      	[COLOR="blue"]wordApp.WindowState = 2 [/COLOR]
      ' Insert the stamp text created above to the end of the document calling the Word macro
      ' generate the footer and attach to the clipboard
      	dim shared vfooter_text as C
      	vfooter_text="[COLOR="red"]YOUR TEXT DATA TO ADD TO THE FOOTER[/COLOR]"
      ' stamp document footer by calling the Word macro , save the document, and quit Word application
      	delete wordApp
      'error handler
      	dim shared vstamp_error as C
          err = error_code_get()
          vstamp_error= error_text_get(err)
          if "Microsoft Word" $ sys_id_enum()
      	end if
          ON ERROR RESUME 0
      ' return document to READ ONLY CONDITION
      Mike W
      "I rebel in at least small things to express to the world that I have not completely surrendered"


        Re: How to find path to MS Word for use with SYS_Shell

        Two other possibilities occur to me:

        (1) Set up a global variable to store the path to Word and have an xdialog that allows the user to locate Word and store the value. I used this method for a long time. There's a screenshot below. It uses ui_get_folder() in the xdialog.

        (2) Use the registry to locate the path. This would require you to know which version of Word (10.0, 11.0, 12.0 etc) is being used or to write code that tests for various versions and presents an interface that allows the user to select the correct one.

        The basic code is pretty simple. In the interactive window:

        dim wpath as c = registry.sys_get("HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word\Options\Programdir")
        ?wpath = "C:\Program Files (x86)\Microsoft Office\Office12\"
        This works in XP and Windows 7 and I'm guessing it's the same for Vista.
        Attached Files