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

Error x7832 - Could not parse

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

    Error x7832 - Could not parse

    I'm new to browser apps, so forgive me for dumb questions, but I'm having trouble creating a UX component with a repeating section. I first get this error message when I do a preview. Is that because I have no parent record to link to the child? The reason I ask is because, when I call the UX component from a grid, I don't get the error. However, I do get a different problem.

    I'm filling the UX with data from a parent grid (Estimate Modules) and the repeating section from a child table (called Parts In Estimates). The parent loads fine, but the child loads and displays ALL the data from the entire table, not just those of the linking field.

    I've attached three pictures:
    (3) is the error message I'm getting
    (5) is the top level binding
    (7) is the lower level or container binding

    The linking fields are Module ID in the parent table (Estimate Modules) linked to the Linked Module field in the child table (Parts in Modules).

    I watched the videos on how to do this, but I think they are old videos because it shows a more complex method of how to do it. I also searched here for this error, but I can't find anything.

    The tables are Access tables, if that matters.

    Any help or direction would be appreciated.
    Attached Files
    Brad Steinfeldt

    #2
    Re: Error x7832 - Could not parse

    I think I figured out the source of my problem, so here are my thoughts. I hope it helps someone else who might land in the trap.

    It must have something to do with the fields I was using to link the parent with the child. I was trying to link it with a field that I created in the table using Access. So, I removed the table bindings and then let Alpha create the tables for me. When doing so, I no longer got any errors. I don't know what I did to the tables, or how I defined them, but it certainly didn't like the way or how I did it. It might have something to do with the my attempt to include the linking fields within the UX Component. Maybe that messed it up, or maybe Access did it.

    If anyone can shed light on this, I'd really like to know. I don't want to fear creating tables only through Alpha just so I can avoid the problem.
    Brad Steinfeldt

    Comment


      #3
      Re: Error x7832 - Could not parse

      Could you post an Access database with your original tables... and the UX... to show the errors. It's tough to know what might be going on without something to look at.

      I'm not a big fan of Alpha with Access tables. Sometimes Access has an odd way of doing things outside it's own container. I get that Access needs to be used sometimes... so if you could post something... that would help.

      Comment


        #4
        Re: Error x7832 - Could not parse

        David,

        I've attached a zip file containing the access database, the UX component (Module_Entry), and the Grid that calls the UX (Modules). I usually get the error when I attempt to save the UX and I'm refreshing the tables when doing the save.

        I've only used Access because I have it. I would love to use something that is more reliable, if it's not too expensive. What would you recommend?

        I'm building this from the ground up, so it would be easy to transition now. I've always used DBF, so this is my first attempt at using SQL. I just feel the need to transition so that I can get the benefits and security of SQL. I'm also concerned that what I've developed in DBF will be obsolete in the next 5 years or so.

        Thanks for looking,

        Brad
        Attached Files
        Brad Steinfeldt

        Comment


          #5
          Re: Error x7832 - Could not parse

          Ok... that's good to know about Access. Let me preface by saying that I've been using Access since its first release. I backed off from it when MS refused to fix a data-killing bug in their runtime. It took them six months to even acknowledge it. Having said that, I would never use Access with Alpha. Maybe to pull data for display... but certainly not as a full-fledged back end. I know lots of people do... but the Access data store was designed decades ago... for the desktop... and for a small number of users... and hasn't really changed.

          You can get MySQL, MariaDB, and SQL Server... all full, unlimited editions... for free. Pick one... it doesn't really matter... they're all excellent. They run locally... and will get you into a real data world.

          Comment


            #6
            Re: Error x7832 - Could not parse

            Overall... the problem isn't Access... but rather all the spaces in everything you're working with... the Database Name, Table Names, Field Names. Spaces are just deadly to systems... as evidenced by the UX not having a clue what to do with them... and therefore showing all records in a Repeating Section.

            Attached is your Access Database, Grid, and UX... with all spaces removed... and now working as expected.

            Some environments, like Access, deal with them... but this just allows for bad habits... so that when you get to systems that no longer look after stuff (Alpha) you get unexpected results.

            Modules.zip

            Comment


              #7
              Re: Error x7832 - Could not parse

              Thanks so much. I knew that...

              I knew that was a danger, but thought if Access can allowing it, I wouldn't have a problem. Shows what can happen when I start thinking. Thanks for fixing my mess as well.

              Also, thanks for the overall advice on Access. I'm going to download and use MySQL instead. I don't want to run into a problem in the future and not know if it's Access or my ignorance. I could at least eliminate one possible problem.
              Brad Steinfeldt

              Comment


                #8
                Re: Error x7832 - Could not parse

                Let me second the foulness of the SPACE in a name - it is amazing how so little NOTHING can wreak so much hell!
                NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

                Comment

                Working...
                X