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

Pack Action Script

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

    Pack Action Script

    I have an action script that does some things like delete records, import, etc.

    During the action script, I run a "pack" of a table. But, after the pack occurs, the action script stops running. The pack appears to work fine and, when removed, all the other functions (after the pack)of the action script work perfectly.

    This is the code used:

    dim tbl as p
    tbl=table.current()
    tbl.pack()
    end

    I've tried variations of the packs' code (removing lines, etc.)but no luck.

    Unfortunatley, I cannot make the pack the last action in the script.

    Any ideas what I'm doing wrong?

    Thanks.

    #2
    RE: Pack Action Script

    You can't pack a table unless you can obtain exclusive use.

    You will have to have other users out of your application, and the table closed from any previous operations. When your pack command attempts to execute, the previous operation in your script must not yet be finished.
    There can be only one.

    Comment


      #3
      RE: Pack Action Script

      John:

      What happens if you take out the word "end" just after the pack... I don't use action scripting much, but it's probably terminating the script...

      Craig

      Comment


        #4
        RE: Pack Action Script

        Then, is there a way to make sure that the other operations are finished before the pack occurs?

        For now, I do not have the prior-to-pack actions running silently. They appear to be finishing before getting to the pack function.

        Could it be that the Post-pack actions attempt to begin before the pack is completed? If so, is there a way to make the pack finish before continuing to the next actions?

        If this helps, the reason for the pack is to re-set an auto-incrementing field to "1" when records are deleted and then new records are appended into the table.

        Thanks.

        Comment


          #5
          RE: Pack Action Script

          Thanks Craig,

          That did the trick. Now everything works like a charm.

          Comment


            #6
            RE: Pack Action Script

            John,

            Sorry I didn't see the real problem in your earlier post.

            As for the exclusive use question...

            Msg ID: 36750
            Subject: RE: table.isopen Not!
            Author: Jerry Brightbill
            Date: 03-08-2001 08:24
            File:

            Nick
            A somewhat simpler way to check if a table is open is to try to open it in exclusive mode. If it is already open you will get an error which you can trap.

            on error goto error_flag

            myflag = .T.
            tbl = table.open(name,FILE_RW_EXCLUSIVE)
            if myflag = .F.
            tbl.close()
            itis = "T"
            else
            itis = "F"
            end if

            trace.writeln(itis)

            error_flag:
            myflag = .F.
            resume next

            This from Jerry covers the question quite nicely. I am "marking as code" the code you would use to enclose the xbasic statements which needed exclusive use of your table, for clarity. Of course you might need to modify the "tbl" pointer name if you had used it elsewhere.

            Stan
            There can be only one.

            Comment

            Working...
            X