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

Global updates and queries

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

  • #16
    RE: Global updates and queries

    Tom

    Please see the attached (zipped BMP file). I don't see a difference between how the operations are designed.

    I tried to use the demo format on my database. It didn't work -- could it be because the form is based on a set?

    I'm working with my personal v4.5. Trying to get the bugs out before I start using V5 and put the database on the server.

    Thanks

    B

    Comment


    • #17
      RE: Global updates and queries

      I'm sorry you're having trouble seeing the differences.
      After you work with saved operations a bit this
      will become second nature.

      1) open each saved update operation in design mode
      - this will show you WHICH FIELDS will be updated
      - it will show you HOW they will be updated
      - it does NOT show you which records will be updated

      2) click 'Update' on the menu bar, then choose 'Select Records'
      - this will show you the range of records which
      will be affected by the saved update operation

      In my little example the lower flags op is defined to run
      against all records; while the raise selected flags op is
      defined to run against only the currently selected records.
      I mistakenly assumed you knew how to find these
      differences, sorry.

      Concerning your question about using a form based on a set,
      I have misgivings about that approach. It adds a level of
      complexity that may be more than you can handle at this stage.
      In fact there are limitations on the types of queries that can be
      run against child tables while using set based forms. These
      may get in your way.

      In my opinion using a saved operation to update selected records
      is appropriate when you want to do a batch update to all qualifying
      records in the table. If you want to update only qualifying
      records that ARE LINKED to the current parent table record,
      I would NOT use a saved update operation.

      It's difficult to offer specific advice because we can't see your
      database. I won't be able to assist further until you can
      either post a working model here, or you email one to me.

      -- tom

      Comment


      • #18
        RE: Global updates and queries

        Tom

        I was unaware of the select records option.. I was looking for it in properties-- but update doesn't have properties.

        I think that I can work around the set issue. It will require training the folks that print the labels. The set draws information from three databases when printing the labels.

        Again, thanks for your help.

        B

        Comment


        • #19
          RE: Global updates and queries

          Bob,

          You're welcome.

          The record selection 'definition' inside the update operation was created by the operations genie. What you're seeing now (in my little example) is how the setting is stored once the genie finishes her work.

          -- tom

          Comment

          Working...
          X