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

Variable type mismatch

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

    Variable type mismatch

    Hi all,

    I have an A5V5 Home Edition application that tracks donations and prints various reports. One of them is a deposit report that requires the data to be manipulated before it is printed.

    To do this I use an empty table that has the desired structure and just write the data that table and then run the report. The report is called from a script that does all the work.

    The table is populated correctly. The report however will not run. If I run it from the Control Panel after the script has run, it runs correctly.

    The script dies on the following line:
    :Report.preview("Grouped Deposit")
    The error is 'variable type mismatch'.

    This is not the most helpful error message! A variable name would be nice. I suspect it is a conflict between the report and the script. I have checked all the tables that are opened looking for a field that might have the same name but be of a different type.

    I have checked all the variables in the report to ensure that when they refer to a field they include the table reference just in case. I have checked the script for variable names that might conflict with the report. I have used debug to look at as many variables as I can think of. I have checked the grouping for the report, the total fields, etc etc.

    Does any one have any idea what else I should be looking for????

    Any help is greatly appreciated.

    Barb Hill
    Tags: None
    #2
    RE: Variable type mismatch

    Hi Barb,

    Not sure why this does not work but I did notice that Report.preview() is now an obsolete function. You might try the replacement PREVIEW_REPORT() function and see if it clears the problem.

    Doug

    Comment

      #3
      RE: Variable type mismatch

      Thanks Doug.

      I replaced the function but still get the same error. No doubt it is something obvious that I'm skipping over when debugging.

      Barb

      Comment

        #4
        RE: Variable type mismatch

        Barb

        What build level are you on?

        Check for updates from the help - check for updates.
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.
        "Make it as simple as possible, but not simpler."
        Albert Einstein

        http://www.iadn.com/images/media/iadn_member.png

        Comment

          #5
          RE: Variable type mismatch

          Thanks. I did that before any thing else.

          Barb

          Comment

            #6
            RE: Variable type mismatch

            Barb

            Can you zip the database and post it or email it directly?
            Al Buchholz
            Bookwood Systems, LTD
            Weekly QReportBuilder Webinars Thursday 1 pm CST

            Occam's Razor - KISS
            Normalize till it hurts - De-normalize till it works.
            Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
            When we triage a problem it is much easier to read sample systems than to read a mind.
            "Make it as simple as possible, but not simpler."
            Albert Einstein

            http://www.iadn.com/images/media/iadn_member.png

            Comment

              #7
              RE: Variable type mismatch

              Al,

              Thanks. I can do that. I will have to change the data before I zip it and send it to you. It is my client's
              contact list so I can't send it as is. It will be later tonight before I can get this done.

              I would prefer emailing it to you. Can I do that from here? If not where can I send it to?

              Thanks for you kind offer.

              Barb

              Comment

                #8
                RE: Variable type mismatch

                I'm not sure whether this matters, but did you close the table in the script before calling on report.preview()? And are the variables in the script and report declared as local variables, shared variables or global variables?

                Comment

                  #9
                  RE: Variable type mismatch

                  Barb

                  I sent a direct email to you regarding how to transfer the zip file.

                  Otherwise clicking on a person's name as listed in the phorum should start your email client with an email addressed to that person.

                  If you didn't get the email I sent to you, respond to this message or email to [email protected]
                  Al Buchholz
                  Bookwood Systems, LTD
                  Weekly QReportBuilder Webinars Thursday 1 pm CST

                  Occam's Razor - KISS
                  Normalize till it hurts - De-normalize till it works.
                  Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                  When we triage a problem it is much easier to read sample systems than to read a mind.
                  "Make it as simple as possible, but not simpler."
                  Albert Einstein

                  http://www.iadn.com/images/media/iadn_member.png

                  Comment

                    #10
                    RE: Variable type mismatch

                    Thanks to all for your suggestions. The problem has... gone away.

                    In addition to checking variables all over the place, I also updated the indexes just in case. No luck. I was preparing to send the database off for Al to look at and I copied it to another computer. I started the application (in the full edition) and it worked. I wondered if it was the difference between the home and full edition so I made a copy on the original computer and ran it with the home edition. The copy worked fine but the original did not.

                    This seems to me that there was something a bit off in the database that was corrected in the copying. Any ideas? Is there a utility to repair databases in A5V5?

                    Barb

                    Comment

                      #11
                      RE: Variable type mismatch

                      Barb

                      I would sound by your fix that there was some corruption in the layout. One utility included in A5 is the ability to compact the database. When you make edits and other changes to a report or other layout, the old layout design code is marked for deletion but not removed. If the database is not compacted, eventually this "junk" accumulates and can cause problems. The solution is to periodically "compact" the database when making design changes, which removes the unused code. Database Compact is available from the control panel menu under "File"

                      Jerry

                      Comment

                      Previous template Next
                      Working...
                      X