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

Table design help needed...

Collapse
X
Collapse
 
  • Page of 4
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 4 template Next
    #46
    Re: Table design help needed...

    Al,

    Judy then gets married to Sam Smith and continues treatments. Her id is now SMI-12345 and new body records get this id, but the existing body records remain JON-12345.
    I see the way it is set up the identifyer would change? Good point!

    Addendum: I haven't used field rules for unique identifiers. I'm seeing the autoincrement is the only field rule that would make it work. I've successfully always used a button based alphanumeric into a user-entered field for unique ID. Gt of the path and get into trouble.
    Last edited by Mike Wilson; 04-26-2007, 06:34 PM.
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    Comment

      #47
      Re: Table design help needed...

      Originally posted by Esio Trot View Post
      If Don reckons he's an bit of a newbie, then I am a super newbie :)

      I don't even have a working application yet, and spend a few hours every couple of days or so working on it - I might even have to start again from scratch (albeit using some forms etc I have already constructed). I have hardly asked any questions, as I do try to "work it out" from examples and the A5 forums

      What I am trying to say is a big thank you to those members for the many generous responses they give. For example, Mike Wilson: I have downloaded his Exam application and added yet again to my knowledge. I really like how he has chosen to not use an auto increment field for the normal client/customer ID field that many applications will have, but uses a calculated field starting with the first three letters of the surname.
      David,
      I started using Alpha about 45 days ago... BUT I began working on the table structure over three months ago(with a programmer). If you haven't already done so, I would make sure you've spent considerable time on that. From my very limited experience in Alpha (and no experience in programming) I can still see the importance of defining your tables and relationships before you design the forms and layout. It sure is tempting to jump right in though. I would have to second your praise of the members of this board. Examples like Mike has provided are truly invaluable to those getting started. Thank you.

      Don

      Comment

        #48
        Re: Table design help needed...

        Yes Don,

        I have been doing tables(was called databases) for years and years. Every project is set to paper before I start. While not always correct, it is a plan. My links between tables usually stands solid. It really messes up when the program changes for ourside reasons and a table has to be added. It goes back to paper.

        You can do some funny stuff in Alpha too.
        example:
        I have inv.dbf attached as a child as 1-1 and it is attached a second time with an alias 1-many. reason is sold car is one to one but there may be 2 or more trades that also need to go into inv.

        example:
        Pho.dbf is really a lookup for manythings. by having the proper fields and filters on lookup. it shows totally different data. loan companies for finance or payoffs, insurance agencies, certain vendors we work with.

        Food for thought.

        Dave Mason
        www.lotrun.com
        Dave Mason
        [email protected]
        Skype is dave.mason46

        Comment

          #49
          Re: Table design help needed...

          Dave Mason,
          Sorry for the confusion... I was actually quoting David Abbot/Esio Trot (Super Newbie :) ) Hey, but thanks for the info you provided.. every bit helps,
          Don

          Comment

            #50
            Re: Application exit help needed...

            Originally posted by Ed Barley View Post
            Anyway, wanted to let Mike know that I have always wondered and never asked how to control the X(Exit) to keep Alpha itself from closing down, and having the control to shut down Alpha through the application. Looking at his example "Exam" data base did the trick.
            I've also copied Mike's Exam application of exiting, messed with it and still learning. I am wanting to modify the code on his EXIT APPLICATION button on the main menu which currently is:

            PHP Code:
            dim vexit as C
            vexit             = p_msg_box("NOTICE","Are you certain you wish to exit ","Exit!exit, Cancel!Cancel","a5_a5icon32")

            if             vexit = "exit" then
                system_event_drop            ("database_canexit","1")
                            'Exit Alpha Five.
                :a5.close()
            end if 
            What I want to do is substitute the command a5.close() in the penultimate line for something that will just close the application, not the A5 program.

            The reason for this is that while I am doing my "try this and see" approach of learning on a dummy duplicate application, it will save me loads of time if I can just swap between applications leaving A5 open.

            It's probably real simple - but I just can't see the wood for the trees.

            Comment

              #51
              Re: Table design help needed...

              Sometimes I feel a real dummy.

              But then, only by putting the problem to paper was I able to see through the trees!!

              The substitution code has been found, and is so simple: A5.DATABASE_CLOSE()

              Thanks for reading :o

              Comment

              Previous 1 2 3 4 template Next
              Working...
              X