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

902nd Embedded Browse Problem

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

    902nd Embedded Browse Problem

    Problem:
    Embedded browse on a FORM has lost link to parent table when adding records using the browse.

    Attached includes a MAIN-MENU. Use the "Enter Transactions" button to go to the form with the troubled browse. Click the hot-spot in the upper left hand corner of the MAIN-MENU to exit to the A5 Control Panel. Password is "frustrated".

    Form name with the embedded browse problem is PAYBILLENTRY3.

    At the time I am submitting this there are 901 threads on the Embedded Browse Problem subject. Needless to say, I did not read each and everyone, but did find that others seem to have had a similar problem and were able to get some sort of resolve by attaching a sample of the problem.

    So here it is, thanks in advance to one and all who would take the time to look at this.
    Tags: None
    #2
    RE: 902nd Embedded Browse Problem

    Barry - the problem is with the set definition for that table.

    I will be interested to see how others would deal with this, but here is my initial look:

    the billno in the parent must exist in another file, so it logically cannot therefore be

    billno + cdate(billdate)

    so neither can the child

    if I were doing this, I would have two fields for the parent:

    billno, as it is
    and billkey
    I would either make billkey a calulated field trim(billno) + cdate(billdate), or write a script in the cansave record event for the parent table in field rules

    ****note - billno and billdate MUST be required
    t=table.current()
    t.billkey=trim(t.billno) + cdate(t.billdate)
    (most likely I would do it this way, in case one of the fields is entered before the other)

    then make the linking fields
    billkey->billno
    or even put a billkey field in the child, also.
    Cole Custom Programming - Terrell, Texas
    972 524 8714
    [email protected]

    ____________________
    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

    Comment

      #3
      RE: 902nd Embedded Browse Problem

      Thanks for your reply Martin.

      Do have BILL_NO, and BILL_DATE defined in both the Header Record (NEWPAY.DBF), and in the Transaction Record (PAYTRX.DBF, also a child table). Have tried using a "key field" TRX_KEY which is calculated thus: BILL_NO+CDATE(BILL_DATE). One of these combinations of linking used to work, not sure I remember which now, as have been busy fixing other things since upgrading to latest version of Alpha 5.

      Read somewhere on this forum that the concatenated fields must be contiguous, maybe that means exactly next to each other in the file, if that is necessary, then I'll have to make that change. Will give it a try, and also look at your suggestion, and hope for other replies, till such time that I can get this to work.

      Thanks again.

      Comment

        #4
        RE: 902nd Embedded Browse Problem

        Well I'm slightly embarassed, looked again at Barry Rochfords article on using more than 0ne linking field, and now have the answer to my problem.

        I may have once had the add mode working for the link, but then had to undue the trick on building (calculating) the key fields that make up the one field link, so as to be able to import fresh data from the old Alpha 4 version of the application. This compounded by concentration on a different aspect of design and/or changing things to work with the latest version may have led to the oversight.

        Somewhat fatigued though by the lack of a function to undue one of the two duplicate functions (CDATE), and (DTOS). That is there seems to be no function to convert a string representation (created by CDATE) of a date such as 09/23/03 (stored by use of CDATE as 200309023) to a date.
        So I'll do the drugery myself.

        Part of my problem is that I get to work on this only briefly every six months or so. Started working at converting the Alpha 4 version of the app. to Alpha 5 (from version 4.5 to 5.0 to the latest patched version of 5.0) some two years ago now.

        Thanks

        Comment

          #5
          RE: 902nd Embedded Browse Problem

          Got the date problem working, thus, ... given that TRX_KEY represents a non trimmed 25 character BILL_NO, +CDATE(BILL_DATE) where a sample could look like:

          billnumber date


          Here is the calculated field rule for BILL_DATE
          CTOD(SUBSTR(Trx_key,30,2)+"/"+Right(Trx_key,2)+"/"+Substr(Trx_key,28,2))

          Hope that this may help someone in a similar situation someday.

          Thanks, my problem is fixed. Now on to the next challenge.

          Comment

            #6
            RE: 902nd Embedded Browse Problem

            Sorry, put my sample TRX_KEY within and it did not display,

            Here it is again

            billnumber billdate(converted with CDATE)
            THISISAPHONYBILLNUMBER 20030923

            Comment

            Previous template Next
            Working...
            X