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

Help with attached file

  • Filter
  • Time
  • Show
Clear All
new posts

  • Help with attached file

    The attached file has one form.

    Kindly go to that form, and what do I need to do to get the top browse to autoincrement the POCD_ID field? This field is then used to link to the bottom browse.

    I need to figure this out before tomorrow a.m.

    Thanks to all


  • #2
    RE: Help with attached file

    forgot the file.

    Hopefully it is here.


    • #3
      RE: Help with attached file

      Tom, I got the file ok, and see what you mean. I don't believe you'll be able to do what you want. Your form is based on a set. You have three browse objects on the form. One for the parent, one for the child (linked one to many) and one for the grandchild (also linked one to many).

      You're trying to add new child records and are frustrated that as the new child record is being entered an autoincrement field is not self-filling. I think this is happening because the form is based on a set.

      If I were facing a short time line, I'd change all the browses to readonly and use the form to display existing records only. I would not do data entry through this form. Instead, I'd add a series of buttons which would call separate forms for data entry into individual tables. Key field values would be passed to the called forms as data entry begins. The browse objects on your main form would be refreshed when the data entry forms close.

      Perhaps others will have suggestions which come closer to what you are shooting for, I'll be watching with interest.

      -- tom


      • #4
        RE: Help with attached file


        I only had time for a very brief look. Your field rules looked a little strange to me. You had lookupc's from your child table to your grandchild table. A child-grandchild relationship implies that the child exists first then grandchildren records are added linked to an existing child. Anyways, I deleted all your field rules in poc_dates and re-added the autoincrement field rule to your POCD_ID field and it worked. Somehow your other field rules are getting in the way. It looks to me like your basic architecture may need some work. The way you are doing it, if the autoincrement malfunctions, you are going to have grandchild records unable to find their parent. In my opinion your grandchild record should have the patient id combined with some unique child element. This was a quick look, but I don't think it's ready for a test drive.



        • #5
          RE: Help with attached file

          Thanks for your thoughts.

          I renamed the POCD_ID field and it works fine. At least for now. Would there be some reason why a fieldname would not work? I know there is an index by the same name, but that is not unusual.

          Hopefully other will respond.



          • #6
            RE: Help with attached file

            Thanks for your input John.

            I'll look at redefining my linking fields and using the patient_ID consistently throughout.



            • #7
              RE: Help with attached file

              Glad you got it going. The index name was also used in some of the lookup calculated fields that you had. Alpha must have seen the name one too many times. Other threads have warned about index tag names, and the guiding theme is to provide unique short names that won't be confused with names of functions or I guess in this case field names.


              • #8
                RE: Help with attached file

                I spoke too soon!

                It won't save records in the POC_Dates table.

                Its getting too late tonight to work much longer. I'll sleep on it.

                Good Night



                • #9
                  RE: Help with attached file

                  Try removing field rules one by one and test if it lets you adda a record. Yuo'll have to do this on both tables. It will eventually work when you get rid of the culprit(s).