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



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

Set indexes

  • Filter
  • Time
  • Show
Clear All
new posts

    Set indexes

    I am working on an application that will be Runtime so the user will have no access to the control panel.

    Each month they will run a join operation which takes a parent table of a one to many set 'A' and joins it to a child table filtered on month providing a single result table for a particular month.

    This result table then becomes the parent table of another set 'B', one to one and the parent is overwritten every month.

    My concerns are are:

    1. Are there any downsides to overwriting the parent table in a set other than creating some orphaned child records.?
    2. Is it essential that the linking field of a parent table of a one to one set has an index.? Because each month the join operation does not copy any indexes.

    In my tests, the new set appears to be content would welcome any advise.


    RE: Set indexes

    Can't answer your question directly, but would suggest this approach.

    Let your join create an intermediate table. Empty the "parentof B set" to which you refer. Append all from the intermediate table.

    Your indexes, field rules, reports, etc, will all be preserved.
    There can be only one.


      RE: Set indexes


      Thanks for your reply, I have tried your suggested route but it has not solved my problem. What I real need is to be reassured that overwriting a parent table of a set on a regular basis is good practise without drawbacks.

      My aim is to grab some data based on records filtered on each month from a one to many table and place it alongside another table as the parent in a one to one set. I can do this by copying the filtered child data each month and overwriting the existing the previous copy. My tests show that it works but as this is a runtime app, I need to be sure of the accuracy.



        RE: Set indexes


        I have not encountered any downside to overwriting a table in a recurrent operation.

        Bill Hanigsberg


          RE: Set indexes

          However, doing so would require that your set be rebuilt each month. Since all code can fail and simple is better than complex, I approach similar problems along the lines suggested by Stan.

          Bill Hanigsberg


            RE: Set indexes

            First, re question 2, A5 will create an index if you don't. You might as well so you can name it what you want (I believe A5 names it based on the field name?).

            As far as the rest, I can't see why you'd end up changing the parent to orphan the child. In our app we have to be able to track every instance of an order. I can see why you might want to so this, however. Perhaps a secondary table with an associated set would be preferable? More info re your app would help here (I can also see why you might not need to maintain historical info re original entries). If needing historical (necessary in transaction processing, but not in, for example, a video collection)) but wanting to modify future references, it is possible that you might want to use a second "parent" table (for current entries) so that historical could be maintained.

            But, other than orphaning some child records, I don't see any problems. (In our system they'd stick out like sore thumbs, indicating that something went wrong and requires manual troubleshooting. We had to add that capability for crashes and user screw-ups. Maybe not in yours.)


              RE: Set indexes

              If we had more info re the type of app you're writing (maybe with attached copy) we could make more constructive comments. It's almost guaranteed that one of the gurus on the site has written a similar app (if not in A5 then in another language).


                RE: Stan, Bill, Jim

                Thanks for you reply to my post last week. I could not reply as I am still having problems getting online and it has taken me time to create a sample.

                I have attached a zip of my sample and it also contains a text file outlining.

                Hope you can find time to have a look.