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

Single Record update Operation Changes the display record to another record.

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

    Single Record update Operation Changes the display record to another record.

    I have a desktop application that updates the current record display on a form with data from another table activated by a button on the form.
    The update operation uses a saved update operation using the current record only for the update.
    The update operation itself works correctly except at the end of the internal function when it refreshes the display.
    This changes the current record.

    In debug the correct record is present at the start of the update operation and only changes after the refresh call.

    As a work around I have tried the record navigation goto record with a saved variable and it never ever returns back to my original saved record even though the goto record function in debug displays the correct record number in the call.

    Any help would be appreciated.
    Jim

    #2
    Re: Single Record update Operation Changes the display record to another record.

    An update operation would not generally be the best choice to do what you describe. Operations are normally performed on a batch of records as opposed to single records.

    It should be fairly simple to assist you with a small script to make changes to the current record based on data from the external table.

    A few necessary details such as the name of the external table, the field names in that table containing values to be retrieved, the field names in both tables containing the linking information as to which record in the external table to use, etc will be helpful.
    There can be only one.

    Comment


      #3
      Re: Single Record update Operation Changes the display record to another record.

      I have a database used to keep track of parts being built. We have both open and finished Parts in this database. Some of this data consists of time estimates and actual times to build these parts. On a newly entered part build we want to create an estimate on how long it may take to build this style of part by the previous ones build to help gauge our costs.
      So I have created on button on a form to just that.
      In The Button
      We create variables for the part displayed and the current record number.
      We then check to see if we have other records like the current part with data in these fields.
      Using tablecount() - This works fine as long as I don't try to exclude the current record in the filter
      with: '.and. (recno() <> var->saved_recno) The (var->current_part = part_no) .and. (has data criteria > 0) works fine.
      if my count is more than 2 I have at least 1 record that I can use for my estimates calculator.
      I then call a save operation to do the counts and sums on the bottom 5 records of this filter criteria.
      I then open a browse on this table to update the default record index for my lookups.
      I close the browse.
      I now try to use a records - Xbasic record change - action in the button code editor.
      I use recno() for the record to update.
      Specify 13 fields to be updated with expressions. Which during debug work fine, the error occurs when doing the tbl.close(.t.) call. An error is generated with a bogus index claimed as not an open index.

      Jim

      Comment


        #4
        Re: Single Record update Operation Changes the display record to another record.

        Additional info the bogus index is not used or required by the data or summation file.
        Jim

        Comment


          #5
          Re: Single Record update Operation Changes the display record to another record.

          Which table are you trying to close with tbl.close(). If it is the table upon which your form is based, you can't close it. The form has it open.
          There can be only one.

          Comment

          Working...
          X