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

Print (To PDF) problem with build 4130

Collapse
X
Collapse
 
  • Page of 2
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
    #16
    Re: Print (To PDF) problem with build 4130

    Originally posted by Steve Workings View Post
    I can't tell from reading your messages:

    Is the print code on a seperate A5W page called by the dialog's AfterValidate event?
    Yes the code I reference above is in the AfterValidate of the component gathering the from/to date and radiobutton for the report selection.

    Comment

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

      George -

      Based on what I saw (I dialed in to his system), the total problem is revealed by the C:\A5Webroot that we saw listed as the session.session_folder. It should be referencing drive D, that's what you have in the server config for the document root. I did some testing and, the session.session_folder is always determined by that document root value.

      First, return the report code to what it was before I edited it (return the chr(92)) to its proper position.

      Then check your server - do you have a 2nd copy of Alpha running, a copy of the full version perhaps, in addition to the WAS? If so, is THAT copy providing the configuration for document root (on drive c)?

      Or, perhaps a different remote session or terminal server session? Check Task Manager (check off See processes for ALL User, if it has that setting) - are there two A5's running. Also, take it out of your startup folder, reboot, make sure WAS or A5 is NOT running, then start the server manually and test.
      Last edited by Steve Wood; 11-07-2006, 07:08 PM. Reason: another idea added
      Steve Wood
      See my profile on IADN

      Comment

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

        George, as promising as I made that sound, it may be completly inaccurate. I "tested" for the value of session.session_folder, but if I made that test using live preview, rather than publishing to the server, and testing there, then the value of session_folder should be the C drive. I'll keep working on it.
        Steve Wood
        See my profile on IADN

        Comment

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

          Thanks Steve(s), I will test this out and post back. Steve sorry for any negative vibes on my statement of your helping with the code, but glad you clarified.

          George

          Comment

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

            I have
            *Removed WAS from my startup and also from any other users
            *Restarted server
            *Checked task manager and tasks under all users to see that only one Alpha was running
            *Reinserted the Chr(92) string in the code & changed dbf to ddd
            *Started my app on a different machine and verified that I was getting a folder built in session_folder on the D drive
            *Added a new a5w page with xbasic of "? session.session_folder", published it and returns "D:\a5webroot\session_folders\7faff58e8c974da59b246bcdaa354d70\"

            Still no report displayed and no report found in the session folder
            ???
            Last edited by George Corder; 11-08-2006, 07:03 AM.

            Comment

              #21
              RESOLVED

              :D

              I resolved this problem today by redownloading and keeping a copy of my original install WAS.exe file from day of purchase. Next I installed the program over my existing install. I first tried to uninstall but the uninstall program kept looking for a install.log file. The install.log file located in c:\Program Files\A5V7WebAppServer would not satisify which I found odd. After installing I ran the server to make sure that the root path and license were intact which they were. I then used the Check for new version link from the systray and redownloaded and installed the current patch (4130_3033). Cleaned my component code up to remove the comments and session_folder testing code out and published. ALL IS WELL! I suppose that somehow the pdf creating section of the program had broken.

              Many thanks to the efforts of Steve Wood and Steve Workings.

              Comment

              Previous 1 2 template Next
              Working...
              X