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

embedded browse link changes

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

    embedded browse link changes

    I am trying to setup a form for a set containing a parent table and 2 child tables. The tables are linked one-to-many with cascading updates/deletes, both on the same level. The linking field is a unique customer number, character type. When I first setup the form the link works fine. When I attach a filter to either child table the link is lost and all the records in the child table are displayed in the browse. I have setup 2 forms and each time once I attach the filters the child tables display all records not just ones with the linking customer number. The tables were originally A4V7 dbf's, the set was created in A5 using the pre-existing A4 dbf's. Is this my problem? Should I setup A5 tables first and import the data? If possible I would like to leave the table/dbf's usable in both A4 and A5.Any help would be appreciated.

    Thank You
    Jeff carroza

    #2
    RE: embedded browse link changes

    Jeff

    Child records are linked to the parent using an index. Depending on how you are applying the filter, you could be changing the child index which could lose the link. Normally applying a filter in form properties works ok. I would also suggest removing the integrity as it freqently creates more problems than it solves.

    Jerry

    Comment


      #3
      RE: embedded browse link changes

      Jerry, I turned off the referential integrity, but the problem still persists. If I turn off all filters the forms display correctly. When I set the filter parameters how can I tell if the index is being changed? Shouldn't the child tables default to the linking index when the form is designed for the set? The filters are not applied to the fields of the linking index.

      Jeff

      Comment


        #4
        RE: embedded browse link changes

        Jeff

        It would be helpful to know more about the structures of the tables, the linking fields /expression, and the exact syntax of the filter. I assume the filter is applied in the filter box in form properties. The best solution would be to zip up the database, the set, and the files in the set with some sample data, and then post it. The only limit is that the zip file must be less than 1 meg. It would be easier to see what is happening with a live application.

        Jerry

        Comment


          #5
          RE: embedded browse link changes

          In my experience, what you are attempting to do will not work. The set links take precedence over any browse filters. I have solved this problem for myself in the past by having the form load or display. Then use xbasic to filter the data displayed with a query. The problem with this approach is that when you change the main table of the sets data, you have to trigger a new query. It will work however.

          Comment


            #6
            RE: embedded browse link changes

            Jerry , I have attached files with sample data. The set consists of a customer file and 2 child files. Cust_rec is for lawn applications/payments; sprays is for tree spray applications/payments. The Entry Form is a tabbed form that I want to display subsets of the child data for additional data entry. Specifically I want to attach a filter to the Cust_rec file to display only records for the current year (designated by a 2 character number as the leading entry in the action field and whether the action is a payment or job done.) When I attach the filter the form displays not the matching records for parent record but all records in the child. I removed the filter in the zipped file. To add back in, go to form design and attach a filter ( *leading(action,"99") to the cust_rec table. I am trying to replicate a system I designed in A4. Eventually I would like the form to include tabs where different subsets of linked child records can be displayed for the data entry person.
            Jeff Carroza

            Comment


              #7
              RE: embedded browse link changes

              Larry, I tried your approach and was able to display the correct data using a range. Is there anyway to attach the xbasic script to the tabs on the form so that each tab would automatically load the desired range? I don't know if this is possible or if I need to have the user trigger the range with a button on the form.

              Thanks
              Jeff Carroza

              Comment


                #8
                RE: embedded browse link changes

                Jeff

                I will take a look at the sample when I get a chance. However, you state;

                "Eventually I would like the form to include tabs where different subsets of linked child records can be displayed for the data entry person."

                You can do this by linking the child table to the parent multiple times using a filter on the link, not the form. However, there is a big caution with this method. I use it in one application and it works ok. However, I do have index problems from time to time since there are multiple indexes open for the same table. If I add or delete a record in a child record, I have to close and reopen the form to allow the indexes to update. Otherwise they get corrupted and sometimes get dropped. I automated this close and reopen and posted the method a long time ago. You may try a seach on filtered links or something like that.

                Jerry

                Comment


                  #9
                  RE: embedded browse link changes

                  Jeff

                  Your filter does work correctly after the indexes were rebuilt. The index structure in a4 and a5 are different. I would suggest not using the same tables in each. Either decide which version you want to use or duplicate the tables in A5 and append the data. If you want to move to a Windows platform, I would suggest using A5V5 unless there is a particular reasion to stay with A5V4.

                  A couple points. When a filter is applied, it will apply to both browses that use the same table link. If you want each browse to display a different group of records with a differnt filter, you will have to link the same table twice, which is not a good idea.

                  You can apply the filter in the link definition in the set, which may or may not be faster and more reliable. You could try both.

                  Your method of linking to the current year requires the year to be hard coded and a year code to be part of the one field. Since you already have a date field, why not try this for a filter.

                  year(Date)=year(date())

                  By the way, I would suggest renaming the date field to something other than just "Date". Although it normaly doesn't give a problem, you can see how easily it is to confuse the field "date" with the function "date()"

                  Jerry

                  Comment

                  Working...
                  X