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

What am I doing wrong

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

    What am I doing wrong

    Having now made the decision to move over to Alpha5V4 from A4v6, I have hit a brick wall.

    In A4v6 to get a child database field to be the same as the corresponding parent, you went to field rules and made the child a calculated field saying it equalled that field in the parent.

    Try as I may I cannot see how A5V4 lets me do this. If I try to do the same (set field rules) as A4V6, I only see the child table.

    It will be something simple of that I am sure.

    Can anyone help?

    Thanks
    Database Software Solutions Limited
    www.dbasesolution.co.uk
    http://www.precise360.co.uk
    PRECISE360 -
    LYNCHPIN -

    #2
    RE: What am I doing wrong

    In A5 you use a lookup expression in a the field rule for a calculated field. You can use the lookupn, lookupc, lookupd, etc depending on whether the value is numeric, character, or date.

    Comment


      #3
      RE: What am I doing wrong

      Right I tried that.

      Dear o dear o dear, and I thought Alpha5 was supposed to be the easy to use relational database!

      Have you read the help page on each of the lookup functions.
      Surely its got to be easier than this?

      Some of us aren't programmers. We just want to get there as simply and as easily as possible.

      So in simple terms I have an A5V4 set and I want to make a field in the child database = a field in the parent.

      The child field = customer
      The parent field = prospect
      The index is called DOCNO
      What's the expression?

      My, I can hardly wait to begin the Xbasic tutorial. I bet that's easy!
      If I wanted to feel confused, inadequate, and depressed... I would have bought Access!!!

      Thanks for your patience.
      Database Software Solutions Limited
      www.dbasesolution.co.uk
      http://www.precise360.co.uk
      PRECISE360 -
      LYNCHPIN -

      Comment


        #4
        RE: What am I doing wrong

        Alex:

        This will be easier in A5 version 5, along the lines of Alpha4. Even so, it is not as bad as it looks.

        You don't mention the names of your tables so I will call them parent.dbf and child.dbf. You put in the real names.

        What I think you want to do is set up a calculated field rule in the parent table which stuffs the value of the customer field in the child table in to the prospect field of the parent table. If I am wrong, say so.

        You wrote:
        The child field = customer
        The parent field = prospect
        The index is called DOCNO
        What's the expression?

        I think something is missing: the name of the linking field between parent and child. If we have that we can insert it in the lookup expression to find the right child record and lookup the value of customer.

        The following should be inserted in the space for the calculated field rule expression in the prospect field of parent.dbf:

        lookupc("f",linkfield_no_quotes,"customer","child.dbf","docno")

        I am sorry I cannot test this for you but I think it is correct. It is certainly *almost* correct but, as you know, almost gathers no bouquets.

        Good luck,
        Bill
        Bill Hanigsberg

        Comment


          #5
          RE: What am I doing wrong

          Hi Bill,
          You're, of course, correct but he wants to go the other way - bring the parent field into the child so it would be:

          lookupc("f",linkfield_no_quotes,"prospect","parent.dbf","docno")

          and the expression would be placed in the field rules of a calculated field in the child table.

          Comment


            #6
            RE: What am I doing wrong

            Whoops; quite so.

            Thanks Ohlen,
            Bill
            Bill Hanigsberg

            Comment


              #7
              RE: What am I doing wrong

              Alex, I prefer to handle this at the form level, instead of in field rules of the child table.


              Assume the existence of a form based on your 'parent' table. If you wanted to add a transaction for that 'parent' you could have a button on the form to open a second form, based on the child table. The script that opens the child table form could stuff values from the parent form into global variables.

              On the child side, when the child table form opens, the onInit or OnActivate events for the form could contain a script which declares an identical set of global variables. These variables can then be 'stuffed' into fields on the form as it is first displayed on screen.


              The effect of this is to 'pass' the values from the parent table form to the child table form, using global variables.


              Later on, when you have more experience with Alpha Five, you will learn that it's possible to read values directly from the parent table form, from the child table form, without using global variables, so long as both forms are open in memory at the same time.


              BTW, I encourage you to visit the Alpha Five vers. 4 message forum. This forum is intended, I believe, for product announcements, not for troubleshooting user databases... You're message threads will have a wider audience if you post them in the vers. 4 forum.


              -- tom




              Comment

              Working...
              X