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

Maximum fillin fields of table lookup(fieldrule)

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

    Maximum fillin fields of table lookup(fieldrule)

    Hi,

    Does someone knows how many(maximum) fillinfields you can set with a table lookup?
    I think 15 because, the 16th field does not get filled.....

    Kind Regards,

    Brendo
    Last edited by B.B.Bongers; 01-29-2007, 06:26 AM.
    Ing./bict Brendo Bongers
    Software Engineer

    http://www.brendobongers.nl

    "There's more than one way to skin a cat."

    #2
    Re: Maximum fillin fields of table lookup(fieldrule)

    Brendon:
    Good question, don't know the answer. A good place to look would be in the help file under maximum, but regardless of what the maximum is there will always be someone who wants to go past that number which make me think of couple questions:

    1-In the field rules, does it allow you to add 16 fields, but when you enter new records it only fill 15? or does it limit you to 15 in the field rules?

    2-Have you tried a "Domino-effect": make field #15 fill another 15 fields once filled? I don't know if this will even work and I don't have need to fill 16 fields, so could you try it and let's know if it works?
    Thanks

    Comment


      #3
      Re: Maximum fillin fields of table lookup(fieldrule)

      Originally posted by G Gabriel View Post
      Brendon:
      Good question, don't know the answer. A good place to look would be in the help file under maximum, but regardless of what the maximum is there will always be someone who wants to go past that number which make me think of couple questions:

      1-In the field rules, does it allow you to add 16 fields, but when you enter new records it only fill 15? or does it limit you to 15 in the field rules?

      2-Have you tried a "Domino-effect": make field #15 fill another 15 fields once filled? I don't know if this will even work and I don't have need to fill 16 fields, so could you try it and let's know if it works?
      Thanks
      Hi Gabriel,


      1. I can add more than 15 fields in the list, but it won't fill the 16th field or higher.

      2. I have switched field 1 to 16, but this had the same effect.

      Regards

      Brendo
      Ing./bict Brendo Bongers
      Software Engineer

      http://www.brendobongers.nl

      "There's more than one way to skin a cat."

      Comment


        #4
        Re: Maximum fillin fields of table lookup(fieldrule)

        The problem was that one of the fields triggered another lookup. When placing that field to the last position of the fill in list, the problem went a away.
        Ing./bict Brendo Bongers
        Software Engineer

        http://www.brendobongers.nl

        "There's more than one way to skin a cat."

        Comment


          #5
          Re: Maximum fillin fields of table lookup(fieldrule)

          Brendo,

          So this means.......you can have 16 fill-in fields...or can have more than 16...did you ever figure out if there is a limit?? Just curious is all as always like to know the limits in case I ever get to that point in an application.
          Appreciate your feedback on why it was "limiting" you in your scenario--nice to have threads with answers in them! :)


          Mike
          Mike
          __________________________________________
          It is only when we forget all our learning that we begin to know.
          It's not what you look at that matters, it's what you see.
          Henry David Thoreau
          __________________________________________



          Comment


            #6
            Re: Maximum fillin fields of table lookup(fieldrule)

            Hi Mike, you are welcome

            Yes, you can have more than 16 fields fillin fields.
            I don't know what the true limit is, it isn't listened in the reference. Maybe Alpha could update their documentation.

            Anyway, It had nothing to do with 16 or more fields, but with a another lookup that was fired by the first fillin lookup.
            That should normally work, but in this case I had to reorder the fillin fields.

            Regards, Brendo
            Last edited by B.B.Bongers; 02-17-2007, 08:34 PM.
            Ing./bict Brendo Bongers
            Software Engineer

            http://www.brendobongers.nl

            "There's more than one way to skin a cat."

            Comment


              #7
              Re: Maximum fillin fields of table lookup(fieldrule)

              I currently fill in a lot more than 16 fields, so I know you can. I don't know the limit, but I am doing about 26.

              Dave
              Dave Mason
              [email protected]
              Skype is dave.mason46

              Comment


                #8
                Re: Maximum fillin fields of table lookup(fieldrule)

                Nice to know Dave.

                Sounds like maybe the limit may be equal to the limit on number of fields on a table (1023)....unless indexes are used then the limit would be 40.
                Even if "only" 40, I wonder how many times this limit would actually cause anyone problems...probably not many.


                Mike

                Edit: do believe 40 index limit is for V4. 47 would be the limit for V5 (per table). Whether these limits have changed since V5 I have no idea but have found no references saying they have.
                Last edited by MikeC; 02-18-2007, 12:05 PM. Reason: more info
                Mike
                __________________________________________
                It is only when we forget all our learning that we begin to know.
                It's not what you look at that matters, it's what you see.
                Henry David Thoreau
                __________________________________________



                Comment


                  #9
                  Re: Maximum fillin fields of table lookup(fieldrule)

                  you could always drop the contents of the record into a variable and then copy it to a new record.

                  Dave
                  Dave Mason
                  [email protected]
                  Skype is dave.mason46

                  Comment


                    #10
                    Re: Maximum fillin fields of table lookup(fieldrule)

                    Hi,
                    It also seems not to work when using Memo fields in lookup? Is this true or is there a way to go around this?

                    Thanks,

                    Edwin

                    Comment


                      #11
                      Re: Maximum fillin fields of table lookup(fieldrule)

                      I never even thought of using a memo field in a lookup. I figured a memo(note) would only be used for current record and if it was something pertinent to the person/thing the record was for I should have a field for it( say 250 characters long ). If the field needed to be longer, I should find out what was going in to it and make more specific fields to hold the data.

                      Not all agree with my methods though.

                      I do fill in fields in my lookup that are lookup fields and they seem to work fine. NONE of my lookup fields "auto pop up".

                      I fill more than 40 fields if that is a question and yes there are 7 indexes and there are 3 on the field I have the lookup set for.

                      Hope I answered the questions.

                      Dave
                      Dave Mason
                      [email protected]
                      Skype is dave.mason46

                      Comment

                      Working...
                      X