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

MySQL/Lookup Issue with New Build

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

    MySQL/Lookup Issue with New Build

    OK, I can't get beyond an issue that has arisen since I've updated to the latest Version 10.5, Build 4040 (2/19). I am using tables in a MySQL database.

    In particular, and to narrow things down, I have built a test project that contains just two web grids. One, the "Lookup Grid", is a simple updateable grid using an AlphaDAO connection string and is connected to the lookup table. The other (the "Master Grid") is an updateable SQL grid with a Detail part, connected to the master table. In the Detail part of this grid I have a field with Lookup checked. The lookup uses the "Lookup Grid" component to fill in a field in the Master Grid. All standard stuff. I have not specified "Restrict Values" for the Lookup and everything works fine. However, if I edit the Master Grid and specify "Restrict Values" for that Lookup and then try to save the grid I get an error message to the effect that a function is not recognized on line 407 (I posted the actual dialog in the "New Patch" thread). If I uncheck "Restrict Values" the grid saves without error.

    I duplicated this setup substituting DBF tables for the MySQL tables and I don't get this error.

    I am willing to admit that this is all my problem but I can't figure out what I'm doing wrong, especially since everything was working fine before I upgraded to this Build.

    Is anyone using MySQL in a web project with the new build AND using Lookups with "Restrict Values"? If so, are there any problems?

    Any help would be much appreciated.

    #2
    Re: MySQL/Lookup Issue with New Build

    Hi Norman,

    Don't be too quick to accept blame for an issue that's been a problem. I believe there are still some problems with the lookup as well as other areas.

    One way to handle it is to redo the item which has the problem and see if it works. If so, perhaps the patch found errors that A5 previously overlooked. If not, I suspect the patch created another opportunity for the staff at Alpha.
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment


      #3
      Re: MySQL/Lookup Issue with New Build

      Originally posted by nlk10010 View Post
      However, if I edit the Master Grid and specify "Restrict Values" for that Lookup and then try to save the grid I get an error message to the effect that a function is not recognized on line 407 (I posted the actual dialog in the "New Patch" thread). If I uncheck "Restrict Values" the grid saves without error.
      Ahhhh yes, the dreaded error 407. I get this off and on as well, even made a couple of posts seeking an answer. Since no solid answer resulted, my unofficial reason for this type of error message is simply that Alpha is saying: "Help, I'm confused and don't now what to do. You're on your own. Good Luck, chap!!" :D
      TYVM :) kenn

      Knowing what you can achieve will not become reality until you imagine and explore.

      Comment


        #4
        Re: MySQL/Lookup Issue with New Build

        Originally posted by forskare View Post
        Hi Norman,

        Don't be too quick to accept blame for an issue that's been a problem. I believe there are still some problems with the lookup as well as other areas.

        One way to handle it is to redo the item which has the problem and see if it works. If so, perhaps the patch found errors that A5 previously overlooked. If not, I suspect the patch created another opportunity for the staff at Alpha.
        Yea, well, as I say, if I untick "Restrict Values" it's fine, if I go back and tick it no go. Same behavior with a brand new, barebones project, as long as it's based on AlphaDAO/MySQL. Never had this error before the new Build.

        I COULD just revert but I don't see long term prospects for my web app (which is an extension of a Delphi desktop program) if I'm going to run into unresolved issues.

        Anyway, appreciate the commiseration.

        Comment


          #5
          Re: MySQL/Lookup Issue with New Build

          Originally posted by nlk10010 View Post
          Yea, well, as I say, if I untick "Restrict Values" it's fine, if I go back and tick it no go. Same behavior with a brand new, barebones project, as long as it's based on AlphaDAO/MySQL. Never had this error before the new Build.
          What is "restrict values"? I don't see that on any of my lookup's definitions.
          Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

          Comment


            #6
            Re: MySQL/Lookup Issue with New Build

            Originally posted by frankbicknell View Post
            What is "restrict values"? I don't see that on any of my lookup's definitions.
            Frank: go into the Detail part of a web grid (read only grid, updateable detail). Select a field (Textbox field). In the LOOKUP section on the right tick the Lookup box, then click Lookup Definition. In the Lookup Behavior section there's an option reading "Restrict Values Allowed". That's the one.

            Are you sure you don't have it?
            Last edited by nlk10010; 02-24-2011, 12:20 PM.

            Comment


              #7
              Re: MySQL/Lookup Issue with New Build

              No, I don't see that option. Can you show me a picture?
              Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

              Comment


                #8
                Re: MySQL/Lookup Issue with New Build

                Originally posted by frankbicknell View Post
                No, I don't see that option. Can you show me a picture?
                Sure. It's in the "Lookup Behavior" section, 3rd option from the bottom (see attached).

                Comment


                  #9
                  Re: MySQL/Lookup Issue with New Build

                  I see now. I have never used the grid type lookup. I will try it tomorrow and see if I get the same error.
                  Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

                  Comment


                    #10
                    Re: MySQL/Lookup Issue with New Build

                    Yes I get the same error when I replicate the process.

                    It is obviously a bug, have you reported it?
                    Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

                    Comment


                      #11
                      Re: MySQL/Lookup Issue with New Build

                      Originally posted by frankbicknell View Post
                      Yes I get the same error when I replicate the process.
                      [ATTACH]27428[/ATTACH]
                      It is obviously a bug, have you reported it?
                      That's not the exact error message I'm getting now, although I DID get it at the beginning. I get the same first part but the last line on mine is "Function not recognized". I must have graduated. :)

                      I have not reported it, however. I'm relatively new here, is there info on these boards or on this site as to how to do that?

                      Thanks for taking the time to try it out and post the results.

                      Comment


                        #12
                        Re: MySQL/Lookup Issue with New Build

                        I did get the 'Function not recognized' error when trying to preview the grid. The error I included in the atttachment occurs when trying to save.

                        Under help, send a bug report. Be very specific in describing what you are doing and what the results are.

                        ps.. If your code gets called immature or naive don't fret it.
                        Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

                        Comment


                          #13
                          Re: MySQL/Lookup Issue with New Build

                          Originally posted by frankbicknell View Post
                          Under help, send a bug report. Be very specific in describing what you are doing and what the results are.

                          ps.. If your code gets called immature or naive don't fret it.
                          Thanks, don't worry, I always consider the source. :)

                          Comment


                            #14
                            Re: MySQL/Lookup Issue with New Build

                            Originally posted by frankbicknell View Post
                            ps.. If your code gets called immature or naive don't fret it.
                            My code has been called a lot worse things than that!
                            Peter
                            AlphaBase Solutions, LLC

                            [email protected]
                            https://www.alphabasesolutions.com


                            Comment

                            Working...
                            X