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

Disappearing Data In Set

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

    Disappearing Data In Set

    I have form that is made up of a set (Invoice -> Acctsrec)
    The acctsrec data is on a tabbed object along with some data from the Invoice table. What happens is this:
    The invoice data has already been saved. After the order has shipped I go back to the tabbed object to enter the acctsrec data. The tab order sequences through about 6 acctsrec fields, then I go to a field (inv_status) that is from the Invoice table. When I tab to the to the inv_status field on the form ALL of the acctsrec data disappears. To correct the problem, when I get to the sixth acctsrec field I do an F9 to save, then I can tab to the inv_status field without any problems. Any ideas why this is happening? I thought the purpose of the SET was to have the availability to mix table data. Am I out in left field.....?

    Thank

    #2
    RE: Disappearing Data In Set

    Philip,

    Check you indexes on each table. Could be that one of the is set to record number.

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment


      #3
      RE: Disappearing Data In Set

      Philip, is the inv_status field involved in the link definition of your set? It sounds to me as though something in your form, or perhaps in a field rule, is causing a new Invoice record to begin, severing the link to the Acctsrec record that was on screen.

      When you form is based on a set, and the record pointer in the parent table moves, the record pointer in the related child table moves automatically. If you add a new parent table record, it's likely that there are no matching child table records yet, so the child table fields become blank.

      In my own work I try very hard never to do data entry using a form based on a set. I'll use such a form (read-only) to navigate... but then I'll use buttons to open subsidiary forms based on one table at a time to do my data entry. why? I got tired of the battle for control over the interface in the set based form. There just seemed to be too many ways for my users to do things out of order. I prefer keeping it simple. One thing at a time.

      -- tom

      Comment


        #4
        RE: Disappearing Data In Set

        All the indexes are correct

        "is the inv_status field involved in the link definition of your set" NO

        "field rule, is causing a new Invoice record to begin," a new invoice record is not created, the inv_status is a simple logical field connected to nothing, it is for informational purpose only.

        "there are no matching child table records yet" The invoice table is the Parent table and the acctsrec is a child tied directly to the invoice table, there is no other table between the invoice and acctsrec table. The relationship is one to one. So the acctsrec info is the only info related to the invoice number.

        "I'll use buttons to open subsidiary forms" this is the concept that I used in A4. The A5 accounting system allows the operators to stay on one form and can do 98% of their work. Saves much time by having not to run around to all the tables for the entry of data. Although there are buttons to get to all the individual tables if the operators have to.

        Comment


          #5
          RE: Disappearing Data In Set

          Philip,
          Do you use a resynch() command anywhere when you save the parent? I had a similar problem on one app that operated like an invoice app. I used resynch() when the parent was saved. For some reason, the child records would display from a different record. I switched to using refresh() on the fields on the form and the problem disappeared.

          Jerry

          Comment


            #6
            RE: Disappearing Data In Set

            Philip,

            Check the events which fire as the user tabs out of the last acctsrec field and enters the inv_status field. It sure seems like the invoice table record pointer is moving. The events to check may be present in several different places:

            1) table field rules (acctsrec)

            2) table field rules (invoices)

            3) form level

            4) form field level

            -- tom

            Comment

            Working...
            X