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

HELP!!! report.saveas not working after upgrading to build 2235-4314

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

    HELP!!! report.saveas not working after upgrading to build 2235-4314

    I upgraded to Build 2235-4314 pre release last week and now everywhere I use report.saveas() function in my Xbasic is giving an error that: 'Argument is incorrect data type' . I have sent a bug report to Alpha but my customers are ringing my phone off (because I had to deploy the upgrade, no choice), and I haven't heard back from Alpha, so I wondered if anyone else could quickly tell me what function I should be using instead??

    Here is an example of some code in Xbasic that has always been working but now gives the error mentioned above:

    Code:
    dim reportLayoutName as c
    reportLayoutName = [I](a character name I calculate so that it is unique, not important to my issue)[/I]
    
    dim reportSavePath as c
    reportLayoutName = [I](does not pertain to current issue)[/I]
    
    
    dim jobCode as c
    jobCode = e._currentRowDataNew.JOB_CODE
    
    'Add arguments to be used in the options.filter
    DIM args as SQL::arguments 
    args.add("whatJob",jobCode)
    
    'identify the options that will be used as the last parameter in the report.saveas line
    dim options as p
    options.filter = "JOB_CODE = :whatJob"
    
    'save the resulting pdf report in the ClientUploads folder
    report.saveas(reportLayoutName, "PDF", "" , "" , reportSavePath,.F.,.F.,args,options)
    Last edited by kingcarol; 06-23-2014, 12:33 PM.
    Carol King
    Developer of Custom Homebuilders' Solutions (CHS)
    http://www.CHSBuilderSoftware.com

    #2
    Re: HELP!!! report.saveas not working after upgrading to build 2235-4314

    Originally posted by kingcarol View Post
    I upgraded to Build 2235-4314 pre release last week and now everywhere I use report.saveas() function in my Xbasic is giving an error that: 'Argument is incorrect data type' . I have sent a bug report to Alpha but my customers are ringing my phone off (because I had to deploy the upgrade, no choice), and I haven't heard back from Alpha, so I wondered if anyone else could quickly tell me what function I should be using instead??

    Here is an example of some code in Xbasic that has always been working but now gives the error mentioned above:

    Code:
    dim reportLayoutName as c
    reportLayoutName = [I](a character name I calculate so that it is unique, not important to my issue)[/I]
    
    dim reportSavePath as c
    reportLayoutName = [I](does not pertain to current issue)[/I]
    
    
    dim jobCode as c
    jobCode = e._currentRowDataNew.JOB_CODE
    
    'Add arguments to be used in the options.filter
    DIM args as SQL::arguments 
    args.add("whatJob",jobCode)
    
    'identify the options that will be used as the last parameter in the report.saveas line
    dim options as p
    options.filter = "JOB_CODE = :whatJob"
    
    'save the resulting pdf report in the ClientUploads folder
    report.saveas(reportLayoutName, "PDF", "" , "" , reportSavePath,.F.,.F.,args,options)

    The only error i see in the message "wrong datatype in the argument" did you change that field type at the DB side. Or perhaps updated the schema between x and y? What happens if you rollback towards the release in use before you updated your webapps. Your sure there is no datatype in that webapps release?

    Comment


      #3
      Re: HELP!!! report.saveas not working after upgrading to build 2235-4314

      Thanks Eric. I just receivec following reply from Jerry at Alpha and am implementing...

      "We recently made a change to force report.saveas() to use the report server, which is previously did not. The change revealed an error in your syntax that previously was ignored.

      report.saveas( Layout_Name as C [, Format as C [, Filter_Expression as C [, Order_Expression as C [, Output_Filename as C [, Open_Application as L [, PrintOptions as P [, Arguments as SQL::Arguments [, Options as P ]]]]]]]] )

      You have


      You passed in .F. for "PrintOptions" and the code is expecting a property. we are changing the new code to handle the error, but you can change the syntax to either of these solutions. Both should work

      dim PrintOptions as p
      report.saveas(reportLayoutName, "PDF", "" , "" , reportSavePath,.F.,PrintOptions,args,options)

      or

      report.saveas(reportLayoutName, "PDF", "" , "" , reportSavePath,.F.,null_value(),args,options)

      "
      Carol King
      Developer of Custom Homebuilders' Solutions (CHS)
      http://www.CHSBuilderSoftware.com

      Comment


        #4
        Re: HELP!!! report.saveas not working after upgrading to build 2235-4314

        Originally posted by kingcarol View Post
        Thanks Eric. I just receivec following reply from Jerry at Alpha and am implementing...

        "We recently made a change to force report.saveas() to use the report server, which is previously did not. The change revealed an error in your syntax that previously was ignored.

        report.saveas( Layout_Name as C [, Format as C [, Filter_Expression as C [, Order_Expression as C [, Output_Filename as C [, Open_Application as L [, PrintOptions as P [, Arguments as SQL::Arguments [, Options as P ]]]]]]]] )

        You have


        You passed in .F. for "PrintOptions" and the code is expecting a property. we are changing the new code to handle the error, but you can change the syntax to either of these solutions. Both should work

        dim PrintOptions as p
        report.saveas(reportLayoutName, "PDF", "" , "" , reportSavePath,.F.,PrintOptions,args,options)

        or

        report.saveas(reportLayoutName, "PDF", "" , "" , reportSavePath,.F.,null_value(),args,options)

        "
        I see that's good news they send by default to the reportserver , great to here it's solved!

        Comment


          #5
          Re: HELP!!! report.saveas not working after upgrading to build 2235-4314

          You should be using a5w_report_saveAs for a web application. report.saveas may work in many cases, but is not safe to use in a web application.

          Comment


            #6
            Re: HELP!!! report.saveas not working after upgrading to build 2235-4314

            Originally posted by DaveF View Post
            You should be using a5w_report_saveAs for a web application. report.saveas may work in many cases, but is not safe to use in a web application.
            Report.saveas now redirects to a5w_report_saveas when running in the app server. It was always safe to use on the app server, but until the latest change always ran in the app server and did not take advantage of the report server capabilities.

            Comment


              #7
              Re: HELP!!! report.saveas not working after upgrading to build 2235-4314

              Originally posted by JerryBrightbill View Post
              Report.saveas now redirects to a5w_report_saveas when running in the app server. It was always safe to use on the app server, but until the latest change always ran in the app server and did not take advantage of the report server capabilities.
              Does the Letter.saveas and Label.saveas also take advantage of the change?

              Comment

              Working...
              X