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

Print (To PDF) problem with build 4130

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

    Print (To PDF) problem with build 4130

    Help!! This problem is on a live website! My customers cannot get their data!

    I had a website that was working on local but not on the server (Firm Support). Then I updated the my build (From v7 3909 to v7 4130) and now neither the local versions or the website versions work.

    The web demo application does not work either (The customer grid with check boxes). Both create a PDF and then redirect to the PDF file.

    The error that I am getting is this:

    500 Internal Server Error
    Script Error
    Error:Error 1498
    ________________________________________
    Alpha Five/7.0 Build/4140-3033 at A502 Port 8080

    I did not get this error when I was running the build 3909.

    Is this a bug in the build or do I need to change something.

    The Print code that gives the error is this:
    <%a5
    if Eval_Valid("Sample_No")
    dim filter as c
    dim order as c
    filter = "Sample_No = " + Quote(Sample_No)
    Order = ""
    Dim filename as c
    filename = session.session_folder + chr(92) + "Man_results.pdf"
    filename = report.saveas("Manure_Auto_Print@[PathAlias.ADB_Path]\Manure_data.dbf","pdf",filter,order,filename,.f.)
    if file.exists(filename)
    response.redirect(session.session_url + "Man_Results.pdf?" + time("hms3"))
    end if
    end
    else
    %>
    <html>
    <head>
    <title>Manure Report</title>
    </head>
    <body>
    <p>Huston we have a problem!</p>
    </body></html>
    <%A5
    end if
    %>

    #2
    Re: Print (To PDF) problem with build 4130

    Dunno about everything, but one error I spy immediately:

    You have this snippet:

    Code:
    "Manure_Auto_Print@[PathAlias.ADB_Path]\Manure_data.dbf"
    Reports are in the data dictionaries. So you should point to the .ddd instead of the .dbf, e.g.:

    Code:
    "Manure_Auto_Print@[PathAlias.ADB_Path]\Manure_data.ddd"
    -Steve
    sigpic

    Comment


      #3
      Re: Print (To PDF) problem with build 4130

      Steve,
      That fucntion is correct it refrences the DBF or the SET not the DDD file.
      Jesse

      Comment


        #4
        Re: Print (To PDF) problem with build 4130

        Jesse,

        I am getting the same error. In my case, the report prints successfully on the local host, but not on the remote (FirmSupport). It used to work when Alpha was hosting, so I suspect some kind of path or permissions problem.

        That's not an answer...but misery loves company!

        Pat
        Pat Bremkamp
        MindKicks Consulting

        Comment


          #5
          Re: Print (To PDF) problem with build 4130

          One of us is missing the other here:

          The code you showed me references the .dbf. It should reference the .ddd.

          Also, I have a bunch of stuff on FirmSupport servers, with no pdf problems.
          -Steve
          sigpic

          Comment


            #6
            Re: Print (To PDF) problem with build 4130

            Yes, switching to .ddd fixed my problem.

            I can only guess that using .dbf worked on the local host because during my testing I had the database open???

            Steve, what's the proper extension for sets?

            Thanks,
            Pat
            Pat Bremkamp
            MindKicks Consulting

            Comment


              #7
              Re: Print (To PDF) problem with build 4130

              You're on track. Refer to the .Set
              -Steve
              sigpic

              Comment


                #8
                Re: Print (To PDF) problem with build 4130

                I am having the same problem. I have a local intranet app that has been working for months. It has been some time since I updated but am on 4130_3033. I can browse and edit data but cannot generate my 2 pdf reports. I enter the from and to dates and choose the radio button of the report I want to see but the page just sits there. The Reset button on my report page does not clear the two date fields like it should either.

                This is the code for my reporting page:
                Code:
                IF eval_valid("fromdate") = .f. .or. eval_valid("todate") = .f. Then
                goto skipreport
                end if 
                dim filter as c 
                dim order as c
                
                Filter = "transdate >= {"+fromdate+"} .and. transdate <= {"+todate+"}"
                Order = "Branchid"
                
                Dim filename as c 
                select
                    case radiobutton3="1"
                    	 filename = session.session_folder + chr(92) + "tempreport.pdf"
                   		 filename = report.saveas("MonthlyTellerActivity@<ADB_Path>\tellertotals.dbf","pdf",filter,order,filename,.f.)
                		 if file.exists(filename) 
                			currentform.RedirectTarget = session.session_url + "tempreport.pdf?" + rand_string(5)
                		end if
                	case radiobutton3="2"
                		 filename = session.session_folder + chr(92) + "tempreport.pdf"
                		 filename = report.saveas("MonthlyTellerReport@<ADB_Path>\tellertotals.dbf","pdf",filter,order,filename,.f.)
                		 if file.exists(filename) 
                		 	currentform.RedirectTarget = session.session_url + "tempreport.pdf?" + rand_string(5)
                		end if
                
                end select
                skipreport:
                Last edited by George Corder; 11-06-2006, 10:15 PM.

                Comment


                  #9
                  Re: Print (To PDF) problem with build 4130

                  George,
                  My problem was with the report itself. Generating the report caused vewrsion 7 problems so the whole system hung. the problem was with a function I used to make a graph on the document. Char_Multi() caused the system to hang. I replaced it with replicate(chr(103),calc->Rate_pH) and every thing worked.
                  Make sure that the report is working first.
                  That is the only help I can give.
                  Jesse

                  Comment


                    #10
                    Re: Print (To PDF) problem with build 4130

                    George -

                    Your scripting is also attempting to pull reports out of dbfs. They don't exist there.

                    Where you have

                    tellertotals.dbf

                    for example, you should have

                    tellertotals.ddd

                    See other pieces of this thread below.
                    -Steve
                    sigpic

                    Comment


                      #11
                      Re: Print (To PDF) problem with build 4130

                      Thanks Steve, I don't know why this has worked for me this long. Steve Wood helped me with this very code here in this thread which I compared to see if my existing code had changed.
                      I altered my component code as follows but still get the same behavior.

                      Code:
                      IF eval_valid("fromdate") = .f. .or. eval_valid("todate") = .f. Then
                      goto skipreport
                      end if 
                      dim filter as c 
                      dim order as c
                      
                      Filter = "transdate >= {"+fromdate+"} .and. transdate <= {"+todate+"}"
                      Order = "Branchid"
                      
                      Dim filename as c 
                      select
                          case radiobutton3="1"
                          	 filename = session.session_folder + chr(92) + "tempreport.pdf"
                         		 filename = report.saveas("MonthlyTellerActivity@<ADB_Path>\tellertotals.ddd","pdf",filter,order,filename,.f.)
                      		 if file.exists(filename) 
                      			currentform.RedirectTarget = session.session_url + "tempreport.pdf?" + rand_string(5)
                      		end if
                      	case radiobutton3="2"
                      		 filename = session.session_folder + chr(92) + "tempreport.pdf"
                      		 filename = report.saveas("MonthlyTellerReport@<ADB_Path>\tellertotals.ddd","pdf",filter,order,filename,.f.)
                      		 if file.exists(filename) 
                      		 	currentform.RedirectTarget = session.session_url + "tempreport.pdf?" + rand_string(5)
                      		end if
                      
                      end select
                      skipreport:

                      Comment


                        #12
                        Re: Print (To PDF) problem with build 4130

                        Where does the value for "radiobutton3" come from? After insuring that radiobutton3 does indeed carry a value, the next thing I'd do is:

                        - Forget the case statements, etc. for a minute, and see if you can just get a script running to print a report. Once you're successful with that, you can start putting the If/EndIf and Case statements around it.

                        - You may find it benficial to use the between() function for your filter. That's probably not the immediate cause of trouble here, but worth using.
                        -Steve
                        sigpic

                        Comment


                          #13
                          Re: Print (To PDF) problem with build 4130

                          It's from my reports.a5w dialog page.

                          Comment


                            #14
                            Re: Print (To PDF) problem with build 4130

                            I can't tell from reading your messages:

                            Is the print code on a seperate A5W page called by the dialog's AfterValidate event? If it is, then it looks to me like you haven't properly shared the radiobutton3 value across pages. It should be set up as a session variable instead.

                            You can help verify whether the value for radiobutton3 is being passed, by putting this code on the print page:

                            <%A5
                            ? "Radiobutton3 Value = " + radiobutton3
                            %>

                            Or, maybe I'm wrong and this is in the dialog's Aftervalidate event. Tell me/us that and I can be more targeted.
                            -Steve
                            sigpic

                            Comment


                              #15
                              Re: Print (To PDF) problem with build 4130

                              Steve Wood helped me with this very code
                              My only help was with the filter.
                              Steve Wood
                              See my profile on IADN

                              Comment

                              Working...
                              X