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

Mail Merge Speed - Lack Of

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

    Mail Merge Speed - Lack Of

    The first time in a session of using Alpha that I do a Mail Merge it takes about 15-20 seconds (sometimes longer) to open M/S Word (2000) on my 3GHZ/512MB SCSI Disk PC - even with nothing else running on the PC. Subsequent Mail Merges in the same session is much quicker - about 1 second.

    In comparison, If I do a mail merge from MYOB (an accounting package) it takes 1 second flat every time - why is A5v6 so slow to invoke M/S Word for the first mail merge - is there any way this can be spead up? - my customers hate it.

    Regards,
    Scott

    #2
    RE: Mail Merge Speed - Lack Of

    Are no other developers customers complaining about this?

    Comment


      #3
      RE: Mail Merge Speed - Lack Of

      You might want to wait more than an hour and a half for a response. ;)

      The initial delay is caused by loading the Word OLE object. Only Microsoft has control over that.
      Aaron Brown
      Alpha Software Development Team

      Comment


        #4
        RE: Mail Merge Speed - Lack Of

        Are there other methods? I wonder what MYOB and the like use to achieve such a fast mail merge process regardless if it is the first time or other?

        Regards,
        Scott

        Comment


          #5
          RE: Mail Merge Speed - Lack Of

          by chance I did a mail merge operation today and it went quickly. The dataset was small, though.

          Bill

          (worse machine than yours)

          By the way, do you detect a difference between versions 5 and 6?
          Bill Hanigsberg

          Comment


            #6
            RE: Mail Merge Speed - Lack Of

            are they using OLE Automation to interact with Word?

            you have the source code to the Word Mail Merge feature in A5. It is only a few lines of Ole automation code. why don't you time which of the commands is taking a long time.

            if it is the intial command that instantiates Word that is taking a long time, you might want to load Word in a background thread when you open your database. then, by the time the user wants to do a mail merge with word, Word will already have been loaded into memory.

            Comment


              #7
              RE: Mail Merge Speed - Lack Of

              It is this command that takes a long time on the first merge:

              merge = doc.MailMerge()

              This would suggest that loading the app on start-up will not help the issue - but I will play with it and see..

              Regards,
              Scott

              Comment


                #8
                RE: Mail Merge Speed - Lack Of

                The only way that anyone is going to be able to tell anything about this one is to run each of the samples from a fresh boot. Otherwise, cache will affect the results, strongly. Now, if MYOB still runs in 1 second and A5V? still takes 20-30 seconds, then there is a real problem.

                Comment


                  #9
                  RE: Mail Merge Speed - Lack Of

                  yes - been there done that. MYOB off a fresh boot with a complex mail merge 2 seconds max. A5 off a fresh boot, simple mail merge (a couple of fields) 20 seconds plus for first merge run (small merge - 1 record only and a couple of fields to be merged from a 20 field table).

                  I do not know if MYOB uses OLE yet - I will need to find out how they do it. I have found that adding:

                  dim app as p
                  app = ole.GetObject("","word.application.9")

                  to the database startup reduces the time down by 5 to 10 seconds - for what ever reason. (.9 refers to the version - not sure if that helps any or not yet).

                  Scott

                  Comment


                    #10
                    RE: Mail Merge Speed - Lack Of

                    I did not recall v5 being slow - and do not have an install of v5 anymore in order to compare - maybe someone who has v5 could do a simple test.

                    Scott

                    Comment


                      #11
                      RE: Mail Merge Speed - Lack Of

                      merge = doc.MailMerge() is a Microsoft Word command. The speed is this command has nothing to do with A5, since the command is being executed by Microsoft Word.

                      Comment


                        #12
                        RE: Mail Merge Speed - Lack Of

                        How to speed up Word Automation by hiding the application

                        http://word.mvps.org/faqs/interdev/MakeAppInvisible.htm
                        Marcel

                        I hear and I forget. I see and I remember. I do and I understand.
                        ---- Confusius ----

                        Comment


                          #13
                          RE: Mail Merge Speed - Lack Of

                          I have tried a few things but to no avail so maybe word is the problem as you suggest . I will have to assume that MYOB has some turbo charged approach to a word merge that we are all not aware of.

                          Scott

                          Comment


                            #14
                            RE: Mail Merge Speed - Lack Of

                            Thanks Marcel - I could not detect much improvement. All a mystery as to why doc.mailmerge() takes so long to execute on the first go.

                            Regards,
                            Scott

                            Comment


                              #15
                              RE: Mail Merge Speed - Lack Of

                              perhaps this is a question that someone at microsoft would care to answer.

                              Comment

                              Working...
                              X