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

Edit-Combo Lookup Definition - Fields, pc.allfields subelement not found

  • Filter
  • Time
  • Show
Clear All
new posts

  • Edit-Combo Lookup Definition - Fields, pc.allfields subelement not found

    I'm working on my first Alpha app for mobile using V12. My app was started whilst I was running a trial version and am now on a licensed version - not sure if this is related to my problem.

    I have a textbox which is configured as a lookup with a type of Edit-Combo List. The lookup definition calls an XBasic function which returns a list of items from a SQL Server database via an AJAX Callback. When I originally configured it I was able to click on the ellipsis button for the 'Fields to display' item and select the fields. Now when I click on this I get an error message stating: "Property Not Found. pc.allfields subelement not found." When I click OK in response to this message the values in the configuration item are replaced with 0.

    This control is currently still working OK when I live preview - I get the expected list of values from the database. I also have the same issue with some other Edit-Combo controls that use different XBasic functions so it's not related specifically to this particular control.

    I want to extend this control to make use of the 'Fill-in Fields' option to populate another control when an item is selected but am unable to do so until I can get this property issue resolved.

    Has anyone seen this issue before & have any suggestions as to what may be causing this?


  • #2
    Re: Edit-Combo Lookup Definition - Fields, pc.allfields subelement not found

    Hey were you able to get this resolved? Having the same error myself



    • #3
      Re: Edit-Combo Lookup Definition - Fields, pc.allfields subelement not found

      No, I didn't find a fix for this. My requirement changed slightly after posting this question so I've not needed to pursue it further as yet. It would be good to get a solution though - if anyone from Alpha is reading.


      • #4
        Re: Edit-Combo Lookup Definition - Fields, pc.allfields subelement not found

        What version of Alpha are you using... build numbers? At the end of your XBasic function, before it returns, try putting in this test code to see if you get the same issue...

        dim txt as c 
        txt = <<%txt%
        yourFunctionName = txt
        The only change you'll need to make in your existing code is commenting out your current function return line.

        You can also add a debug(1) statement to your XBasic function and walk through to ensure stuff is ok.


        • #5
          Re: Edit-Combo Lookup Definition - Fields, pc.allfields subelement not found

          Hi David

          I'm running V12.3 Build 2999 (System Addins build 4519).

          I tried your suggestion and this made no difference. The lookup and the XBasic function (my original) actually works fine in the application - the combo is populated with the expected data from my SQL Server database.

          The problem only occurs in the designer - see screenshot for more info. I've also tried creating a new combo textbox and get the error in the designer as soon as I do the same selections.

          Another test I tried was creating a new app from scratch and added a textbox as a lookup with the sample code - as you provided. This time it worked fine so it looks like it's something to do with my application configuration - a corruption somewhere perhaps?



          • #6
            Re: Edit-Combo Lookup Definition - Fields, pc.allfields subelement not found

            I'm not getting this error with test data. Another suggestion is for you to dump your SQL table (with or without data, doesn't matter) and post the table and your XBasic code. This way, your XBasic code and table can be used in a test.


            • #7
              Re: Edit-Combo Lookup Definition - Fields, pc.allfields subelement not found

              OK, so I tried stripping out a lot of the irrelevant controls in a copy of the app to create a smaller package that would demonstrate the error and now the error has disappeared - the designer dialog works OK now. It looks like I'll have to start again with a fresh copy and try & narrow it down - there's obviously something in the app setup that's causing this.

              I'll post again if I manage to locate the cause of the error.

              Thanks for your input David.


              • #8
                Re: Edit-Combo Lookup Definition - Fields, pc.allfields subelement not found

                I am getting a similar error when I use the edit combo box builder with an xbasic function:


                Are other people having similar issues? Is this a bug?