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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Don't use referential integrity with cascade changes and deletes!

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Don't use referential integrity with cascade changes and deletes!

    At least not with the last two builds. It will cause data loss. If you have a form based on a set ,and who doesn't, if you edit information on the form from the parent table, linked information in the child tables will be overwritten with the information from the next consecutive record of their respective tables.
    Tags: None
    #2
    Re: Don't use referential integrity with cascade changes and deletes!

    Gary,

    Could you please post a sample here to demonstrate exactly what it is you are describing.

    Also, have you reported this, with a working sample?
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment

      #3
      Re: Don't use referential integrity with cascade changes and deletes!

      I have the same problem, sent in a sample to bug report and never even got a reply from support, so I can only assum this is a big problem.

      Comment

        #4
        Re: Don't use referential integrity with cascade changes and deletes!

        Hi Greg,

        Could you please give me a step by step in Alpha Sports as to how to duplicate this problem.

        I have have yet to not have a reply from a bug report, however large or small.

        Did you ever follow it up?
        Regards
        Keith Hubert
        Alpha Guild Member
        London.
        KHDB Management Systems
        Skype = keith.hubert


        For your day-to-day Needs, you Need an Alpha Database!

        Comment

          #5
          Re: Don't use referential integrity with cascade changes and deletes!

          Not sure if this is related but I don't seem to have as many issues with records that others are showing. I am using the latest build. The one key thing that I turned off was the autobackup feature that came with the new version. I did so because of a post on speed but it basically said

          Layouts - Auto Backup - V10 introduced auto backup of Layouts (Forms, Reports, Browse, Label, Letters, and Field Rules) - You can now turn off this feature using the a5.system_mode_set() command.
          Examples:
          'Check status of feature
          ? a5.System_Mode_Get("auto_backup")
          = "True"
          'Turn feature off
          a5.System_Mode_set("auto_backup","false")
          It may be that this process is causing issues and it may not, but food for thought for this topic.
          -----------------------------------------------
          Regards
          Mark Pearson
          [email protected]
          Youtube channel
          Website

          Comment

            #6
            Re: Don't use referential integrity with cascade changes and deletes!

            New patch 2814-3539 addresses this problem. Read release note below:

            "Forms - Sets - Cascade Delete Field Rules - If the 'Cascade Delete' option was enabled in the set, edits to the primary table in the set were sometimes lost."

            In my case it wasn't the edits in the primary table that were lost, it was the data in the browses linked to the primary table that was lost. As soon as a edit was started the linked browse data was replaced the next consecutive record in the table.
            I haven't downloaded it yet, but as soon as I do, I'll let you know if it fixes the problem. This was not an issue in build 2736-3523 that was running on another computer, but in the last two builds (2783-3536 and 2787-3538) that I installed on another computer, it definitely was a problem. But one good thing, I studied alphasports a little more and made my form work more like it and turns out it was a nice work around. I believe I might just keep it :)
            The other alternative was to change the "cascade changes/delete" rule to "prevent changes" or turn it off altogether in the set rules. Probably, in my case wouldn't have made a difference, but the rules should work without causing one a problem that could be damaging as for as loss of data is concerned.

            Comment

              #7
              Re: Don't use referential integrity with cascade changes and deletes! Cured

              New patch 2814-3539 cured the problem, now to see if it broke anything else

              Comment

                #8
                Re: Don't use referential integrity with cascade changes and deletes! Cured

                Originally posted by gskelton View Post
                New patch 2814-3539 cured the problem, now to see if it broke anything else
                Hi Gary,

                I'm looking to roll this new latest one out. Find any "nasties" in there? My testing seems good up to now.

                Thanks

                Bill

                Comment

                Previous template Next
                Working...
                X