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

Trace Window Error

  • Filter
  • Time
  • Show
Clear All
new posts

  • Trace Window Error

    I am getting a couple of Trace Window Errors. I notice I get one of the following every time I do a lookup.

    table_lookup.onclose(Table_Lookup.this) : Too many parameters

    None of the lookups have more than a dozen fields or so. What could be causing this error?

  • #2
    RE: Trace Window Error

    I'm not familiar with the function you are using, but "too many parameters" means you have specified too many parameters in the function.


    • #3
      RE: Trace Window Error

      What is the actual code you are using for your table lookup?
      #1 Designs By Pagecrazy


      • #4
        RE: Trace Window Error

        The only code is the Lookup tab in field rules. That is the only tab with anything on it. The lookup is just like all the others that I have, but they do not seem to have any problems.


        • #5
          RE: Trace Window Error

          Can you take a screen shot of the field rule lookup for that field that you are using? That may allow us to help a little easier.
          #1 Designs By Pagecrazy


          • #6
            RE: Trace Window Error

            Here is the screen shot.


            • #7
              RE: Trace Window Error

              I am wondering if it has anything to do with the number of fields you are actually displaying. I know that you should not have difficulty with the filling side of it, but I have not personally displayed all the fields that I am filling.

              Does the lookup actually work and you just get errors in the trace window?

              I would try some of the following things first:

              1) reset your lookup .... by this I mean to re-set the table, linking field, sort order ....

              2) then I would reset each of the linking fields

              3) save the field rules

              4) re-evaluate the field rules

              5) PACK both tables.

              6) compact the db

              7) re-try the lookup and see if you still get the errors.

              If you still have the problem after the above, maybe you can change the lookup so that you only display a few of the fields ... you can 'fill' them all but maybe just display 2 or 3 of the main fields that will give you the data you need in order to make your selection.

              If that does not work, then zip your db and attach it here so we can play around with the tables and field rules. If you can provide us with the steps we need to take, ie which form etc ... then we can duplicate the problem and find a resolution for you.

              Good luck
              #1 Designs By Pagecrazy


              • #8
                RE: Trace Window Error

                I am only looking up 15 fields and displaying only about 5 or 6 items. Of the list above I would say that everything display's but does not import. From what I can see there should not be any problems. I am attaching the Trace Errors and Events generated by just the lookup action.


                • #9
                  RE: Trace Window Error

                  I resolved part of the problem as my field rules width and the structure length did not match. I corrected this only to still get the same errors. To the user nothing is strange or out of the ordinary.


                  • #10
                    RE: Trace Window Error


                    The error says there are too many parameters. One thing I noticed in the trace is that in the qu_head record number 18 appears a lot. I would guess that the error has something to do with that record. Maybe it is corrupt of there are different fields in that record or something, I really have no idea, but I would say to check out that record thoroughly.

                    Also, did you try to pack the table as suggested in my earlier post? If there is a corrupt record packing will sometimes fix this for you.

                    Let us know how you do.
                    #1 Designs By Pagecrazy


                    • #11
                      RE: Trace Window Error

                      I have compared the field lengths and field types (Character)on both databases. They match. I have looked at the form to make sure that the fields match the database and they do.

                      The event that is blank I don't know what it might be and the one with "Eagle Cliff Manor Add" I have double checked the field rules. The only rule it has is to skip if another field (Edit)= False (.F.)

                      What if there was a field that was copied on top of itself? I have copied forms from other area's and I have noticed that it creates a duplicate. Once I erase the duplicate it seems to work fine. I have also checked this form for this issue and it does not seem to be present.


                      • #12
                        RE: Trace Window Error

                        Any other idea's that I can check?