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

Continued Report Problems in 8099

Collapse
X
Collapse
 
  • Page of 5
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 4 5 template Next
    #31
    I just realized I have been using AS for almost 10 years now! "a5v12" was the default folder back then, lol
    NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

    Comment

      #32
      I am also using a5v12. Not sure why that would make a difference. I will cleans things up and install in the default folder.

      Comment

        #33
        If it means anything at all - this was true first on my dev machine here at home - which prompted me to do the same on my server...when I saw the immediate difference locally I knew that typically if it runs locally it will run live on the server as well when running identical an setup - perhaps there are paths involved that affect things - for instance curl files will result in a statement like
        ce.setOpt("CAINFO","C:\\Program Files (x86)\\Alpha Anywhere\\CARoot\\ca-cert.pem")
        ce.setOpt("CAPATH","C:\\Program Files (x86)\\Alpha Anywhere\\CARoot")

        and if you look "Alpha Anywhere" is the root folder of the server so if it read "a5v12" that curl file would not work.

        This could be stumbling block to success in changing paths. It could be that there are other places in the AA code building process that once written into a UX might not resolve anymore resulting in odd behavior and perceived bugs, especially if the dev machine and the server are using different paths to the server files. I am guessing at this point on that - all I do know is it worked.

        Let us know how it goes!
        NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

        Comment

          #34
          I installed the WAS on my production server in the default folder. I did not delete the folder \a5V12 ApplicationServer I had been using, but I renamed it.

          I am still seeing text in reports with spacing problems:
          TextOverlaps.png

          I hope this will be fixed in a future stable release.

          But I am still seeing reports with sections that fail to render when running the WAS via AlwaysUp. So I created some fake data to demonstrate.

          Here is a report rendered with the WAS running 8099, but not managed by AlwaysUp:

          ConverWebServer8099NoAlwaysUp.png


          Same report, this time with AlwayUp running the WAS:

          ConverWebServer8099WithAlwaysUp.png
          The object that doesn't render is an RTF object, but there are RTF objects, the address and phone numbers, that do render.

          Comment

            #35
            Question: When you run an instance started in "Always Up" - Is it running in the current session or "session 0"
            Other Question: Since you renamed the previous installation is it still recognized in the universal installer as an installed product?
            NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

            Comment

              #36
              Is always up running the correct server build - remember file locations have changed.

              Insanity: doing the same thing over and over again and expecting different results.
              Albert Einstein, (attributed)
              US (German-born) physicist (1879 - 1955)

              Comment

                #37
                Pete - yes I have changed the path so it points to the correct file.

                "Always Up" - Is it running in the current session or "session 0"
                Running in the current session made a difference! The reports render all the objects. I had not tried that.

                Not sure where to go from here. AlwaysUp starts in Session 0 when the machine is booted.

                AlwaysUP is using an administrator login. The user name starts with .\.

                And of course 7902 has no problem in Session 0. This is only an issue running 8099.

                Comment

                  #38
                  Well if it's not a feature - it's a bug in transition.. AA need to address it. Again, it looks messy. On the list of fixes I'd say its a 10/10 - sadly developer clients will not accept it in the end and move on.. to where the problem isn't.
                  Just saying - Pete
                  Insanity: doing the same thing over and over again and expecting different results.
                  Albert Einstein, (attributed)
                  US (German-born) physicist (1879 - 1955)

                  Comment

                    #39
                    I really don't know what the root cause is from server version to another but, I do know that I setup mine to always run in the current session. You can do the same, it's not too difficult and you can see the server in the application tray in windows which makes it easy to tweak settings or look at logs.

                    https://www.coretechnologies.com/pro...onAtLogon.html
                    NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

                    Comment

                      #40
                      ...always run in the current session
                      I will try this, but it looks like it requires a login to run it. I need it to run the WAS on boot, without requiring a login.

                      Comment

                        #41
                        AlwaysUp is pretty cool....
                        AlwaysUp includes native support for automatically logging you in and starting your GUI applications when your PC boots. Simply select Autologon... from the Tools menu to bring up the Autologon window, enter the credentials of the user to be logged on and check the Launch all auto-start applications... checkbox...
                        https://www.coretechnologies.com/pro...#AvoidSession0

                        Comment

                          #42
                          how often does the server reboot? It's no more than the login credentials to the server itself - seems like an easy fix. I do think this has something to do with how the print server starts, session 0 may not have access to it. I am pretty sure the keyboard and mouse don't even work in session 0
                          NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

                          Comment

                            #43
                            What is going on with this printing issue where it drops the leading and ending characters from view.
                            This has been an issue for months now. Is there a fix other than modifying hundreds of reports manually.
                            I have complaints everyday from my customers. Why is there no official release to fix this problem for months?
                            Chad Brown
                            • Likes 1

                            Comment

                              #44
                              Looks like the July 11th release fixed these reporting issues for me (8245).

                              Comment

                                #45
                                I will be testing 8425 this weekend. I didn't see anything specific in the release notes about printing issues, but I have hope.

                                Comment

                                Previous 1 2 3 4 5 template Next
                                Working...
                                X