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

Limitations on Set Definitions

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

    Limitations on Set Definitions

    Upon upgrading from V5 to V10, I found it strange that V10 no longer seems to support the use of UDF's nor global variables in expressions used to link the parent & child tables.

    Under V5, I freely used such when building expressions by which to link the tables. Upon transferring the sets to V10, everything seems to work fine - the child tables appear to be properly linked when browsing the set.

    However, if I go into the set definition and attempt to edit the linking expressions, the presence of any global variable or UDF will make it come back with a dialog message reading "Parent expression: Function is not recognized". So I cannot edit the expression so long as it remains to have global variables or UDF's.

    In the help, I see a warnings that "linking fields ... cannot be calculated fields" and "linking fields ... cannot be auto-sequence fields" but I do not see where that would apply to expressions. Any thoughts?
    Tags: None
    #2
    Re: Limitations on Set Definitions

    Sounds to me like it might be worth a bug report. It may be too late to get it fixed in v10 now but at least they might do it for v11.

    Comment

      #3
      Re: Limitations on Set Definitions

      Thanks, Cal. No thanks, Alpha.

      For our large system (200+ users), we are about to implement V10 and cannot think about a V11 upgrade. If it is a bug, I will be tempted to make field rule edits on V5 and see if I can somehow get it copied to the V10. (I couldn't simply copy the SET file without affecting the layouts.)

      Steve
      Last edited by Steve Andrews; 07-20-2011, 01:36 PM.

      Comment

        #4
        Re: Limitations on Set Definitions

        I did find a tedious workaround which will do for now. Since it's rare that I run into this, I will use this workaround for the critical sets for which it is essential. What I did was:

        - I made necessary edits to the Parent Link Expression on the V5 version.
        - I copied this set to a temporary subdirectory.
        - I renamed the set with a "_v5" suffix to distinguish it.
        - I loaded this set ("myset_v5") into the V10 application.
        - Upon editing "myset_v5", I go to the child table with the new link.
        - I right-click the "Parent Link Expression" label (not the expression itself).
        - I select "Copy".
        - Then I edit the original set ("myset"), going to the child table in question.
        - By right-clicking "Parent Link Expression" and choosing "Paste", it changes.
        - Then I save "myset" and all is done.

        When doing the paste (without editing), the new expression fills in without the messages appearing (which thereby prevent the changes). Thus, the change has been accomplished. Through a browse, I verified that the linked table is properly set up. Whew!

        Steve

        Comment

          #5
          Re: Limitations on Set Definitions

          Have you tried to:
          1-Remove the expression and use a one-field link, Save, then
          2-Go back and edit the set and use an expression for the link (and you could use copy/paste here if it works)

          Or:
          1-Delete the link altogether
          2-Then relink with the expression

          A lot of times, and not just in linking fields, but sometimes in the expression window, the field rules..etc.. for some reason alpha does not recognize elements of the expression and throws an error. The trick is to bypass that and save the expression assuming it's valid. Sometimes you can, sometimes you can't until you fiddle around a little bit.

          Sorry, don't have v10 to test.

          That said, where are these global variables dimmed?
          Do they show in the IW?
          Have you tried to dim them in the IW before editing the set?

          Would it be better to use an intermediary table containing the values of these variables, instead of the variables?
          If all fails, that might be a workaround for the other sets.

          Comment

            #6
            Re: Limitations on Set Definitions

            Thanks, Gabe. I will give those ideas a try later today.

            Comment

              #7
              Re: Limitations on Set Definitions

              Yes, the globals show up in the IW but it still failed. However, I found an easier workaround.

              Upon trying to edit the link expression, I type in whatever expression I want to use - even if it involves UDF's and global variables. Instead of trying to save it (which results in the error message), I copy the expression. Then I cancel the edit, right-click "Parent Link Expression", and select Paste. The expression then gets assigned. I can do the same on the Child Link Expression if it needs editing.

              I did the above on a fully new set for testing purposes. Upon browsing the set, I saw that the child table was properly linked taking the global variable into consideration.

              So using copy/paste rather than the OK button for normal editing seems to get you around some incorrect edit checks Alpha has put in.

              Steve

              Comment

                #8
                Re: Limitations on Set Definitions

                I found that to be true before. I can't explain why it works this way but it sounds that the original references of the set were retained and when you enter, even though it's copy/paste, the correct references overwrites the previous ones.

                Comment

                Previous template Next
                Working...
                X