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

displaying index update messages

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

  • displaying index update messages

    I have on a menu form under a frame called 'Utilities' a button labeled "Update Indexes" whose actions script i have below. Problem with the script is that it stops after the current file is indexed and you have to press the "OK" button to continue.

    What i want to do is to display the message about which file is indexing while that file is being indexed and change as each subsequent file is indexed to the end where the "Done" message is displayed.

    any insight to a solution will be greatly appreciated.


    'Xbasic

    dim tbl as p
    dim response as n
    dim files as p
    dim table_name as c

    response=ui_msg_box("Warning","You need exclusive database access. Make sure you are the ONLY user running the system. This process may take a few minutes.",305)

    if response=2 then
    end
    end if

    if response = 1 then
    hourglass_cursor(.T.)
    on error goto noproblem
    a_tbl = table.open("biro_97.dbf")
    ui_msg_box("System Indexing Progress","Now indexing the biro_97.dbf")
    a_tbl.update_production_index()
    a_tbl.close()

    a_tbl = table.open("bizerba.dbf")
    ui_msg_box("System Indexing Progress","Now Indexing the bizerba.dbf")
    a_tbl.update_production_index()
    a_tbl.close()


    Other 47 files to be updated


    end if

    hourglass_cursor(.F.)

    ui_msg_box("Reindexing Files","Done!.", UI_OK+UI_ATTENTION_SYMBOL)

    end

    noproblem:

    resume next


  • #2
    RE: displaying index update messages

    Don,

    The ui_msg_box() will always stop the script.

    I would suggest you build a form with nothing but an RTF box on it. On the RTF box, put some basic text and a global variable. Before running the index updates, assign some appropriate text to the global variable and open the form. (I suggest assigning a pointer to the form.) Then as each index update is started, revise the text.

    Here is a concept script and the attached file has a "Please_wait" form that I use.

    DIM g_text as c
    g_text = "Updating XYZ Index"
    fp = form.view( "Please_Wait" )
    "
    g_text = "Updating ABC Index"
    fp:g_text.refresh()
    "
    etc.,
    etc.,
    fp.close()

    Don't forget that last line to close the "message" form.

    Comment


    • #3
      RE: displaying index update messages

      Don,

      The use of ui_msg_box in this instance doesn't work well as you have found, since all activity stops until the ok is clicked. There are a couple alternatives since it appears all you want to do is give the user a message. One easy way is to send the message to the status bar using

      statusbar.enable()
      Statusbar.set_text("your message")
      statusbar.disable()

      Another possibility is to put a text box on the form and write the text to the text box. When you are done, hide the text box. A third alternative is to create a small form with the messages and then use the xbasic to open and close the form as needed. I use both the first and last idea together and users seem to like it.

      Jerry

      Comment


      • #4
        RE: displaying index update messages

        Sorry, I got the HTML wrong - here's the script again.

        Here is a concept script and the attached file (previous message) has a "Please_wait" form that I use.

        DIM g_text as c
        g_text = "Updating XYZ Index"
        fp = form.view( "Please_Wait" )
        "routine to update index>
        g_text = "Updating ABC Index"
        fp:g_text.refresh()
        "routine to update index>
        etc.,
        etc.,
        fp.close()

        Don't forget that last line to close the "message" form.

        Comment


        • #5
          RE: displaying index update messages

          WOOT thanx Cal u r a life saver hehehe or something like that anyway that is exactly what i was looking for.

          Comment

          Working...
          X