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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Report Error

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Report Error

    I have been wrestling with this error for several months and can not figure out what is happening.
    I am on build 4866 using IIS and I have 3 reports that randomly trigger the following error:

    Report did not print. Error reported was:
    Layout name: C:\inetpub\Default Web Site\ContractPrint.a5rpt Layout type: report
    create_table(tempfilename,tableStructure)=.f.: Too few parameters at line: 552

    I have not been able to identify the pattern of the error as it is reported randomly. In testing, it is very rare that the error appears and when it does, running the report again typically works.
    I am using the Action Javascript "Open a Report, Label or Letter Layout".
    I have over 40 reports and only 3 produce the error randomly.
    I have rebuilt the reports and changed them from Layout to Free-Form with no change

    The Xbasic Error log on IIS shows 2 errors:
    1) Script: a5w_SQL_TableFromResultSet() line 131create_table(tempfilename,tableStructure)=.f.: Too few parameters
    2) The error that the report gave i.e. create_table

    It appears that the a5w_SQL_TableFromResultSet is initiating the error.
    Does anyone have any idea of what I can do here? Is this a SQL communication error?
    I believe that this error started when I switched my database from mySql to mariaDB but I can't be sure.

    Rob
    Tags: None
    #2
    Re: Report Error

    I would look at all of the field names of the report.

    Are any of them reserved words? You would think that would give an error every time, but maybe not.

    Does the data contain any issues that might be causing a problem? Is there a LOT of data - as in it is timing out, or does the error happen even with few records?

    Comment

      #3
      Re: Report Error

      Hi Larry,

      Thanks for the reply.
      The field names are quite unique and definitely not reserved words.
      the data looks good. There is a field that typically returns [Null] in sql but you would think that would error every time.
      It doesn't matter if there is 1 record or 100, still randomly errors on first try (usually after a fresh login i.e. new session).
      I have xbasic code running prior to the action Javascript running the report so I put a delay in there to see if that solved it, but a 2 second delay did nothing.

      Rob

      Comment

        #4
        Re: Report Error

        I'm not sure I can help then. I don't use the IIS version.

        In case you don't know how Alpha reports work:

        Alpha queries the database and gets a set of records. It then turns those records into it's own table which it runs the report from. (Thus the create table.)

        I wonder if it's a permission issue of some type. Maybe if you run the report and it's the first thing that Alpha has to write into the session directory it hasn't secured proper permissions yet. But if you write in some other way first it secures and keeps the permissions.

        Note: I am not sure all of the factors that would cause Alpha to write something to the session directory.

        Comment

          #5
          Re: Report Error

          Ok, thanks for the info. Do you know if you can run a report manually from xbasic instead of using action javascript?

          Comment

            #6
            Re: Report Error

            If you setup a report in action javascript, you can turn it into javascript code and run that instead.

            Then you could at least put alerts in the javascript to see exactly where it is failing.

            Comment

              #7
              Re: Report Error

              The action javascript code converts to:

              {grid.componentName}_O_7EA24F6885D74ACD96D9674EE83E0679({grid.rownumber},'{grid.rowId}',this);

              I will put a debugger command in there and see what is happening. I believe this is in the A5 script and cannot be changed.

              Rob

              Comment

                #8
                Re: Report Error

                From the action javascript, click on view javascript (a link on the upper right of the window)

                Then go to global declarations.

                There is a bit more detail in there ….

                Comment

                  #9
                  Re: Report Error

                  I didn't know that existed, thanks. I think it is a permissions thing on the server though. I am going to fiddle with the permissions settings and see if that is what it is.

                  Thanks for your help.

                  Rob

                  Comment

                    #10
                    Re: Report Error

                    I had reports that worked just fine and then an update started causing this problem. I really think this is a timing issue.

                    Comment

                    Previous template Next
                    Working...
                    X