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

Release Candidate for Next Update

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

    #16
    Re: Release Candidate for Next Update

    i have install the beta patches on both my Development machine and my VPS - Application Server. I think that most of the problems are solved. No fatal errors are coming out now with using grid linkers etc...
    However on my local machine when I test the application, PDF reports are shown normally.. But after publishing to VPS I do get errors - unable to print PDF reports.
    I uninstalled once again application server form VPS - reinstall it again and then used the beta patch but nothing happened.
    Something more to do on this PDF report print error??

    This is the actual error report:
    Report did not print. Error reported was:


    Layout name: Report4@[PathAlias.ADB_Path]\doctorsall2009.ddd
    Layout type: report
    OLE Automation Error. Source is CDINTF~2." DriverInit failed"

    What to do next?

    Regards
    Marios Karaiskakis
    Last edited by Karaiskakis; 02-20-2010, 05:55 AM.

    Comment


      #17
      Re: Release Candidate for Next Update

      I'm getting exactly the same error messages re reports on the WAS

      Comment


        #18
        Re: Release Candidate for Next Update

        Downloaded the beta and installed. When I open a grid that is made with an earlier version it takes a lot longer to open the Live Preview, and the search box now disappears of the right side of the screen

        Comment


          #19
          Re: Release Candidate for Next Update

          If you have found a bug, please use the "Send a Bug Report" help menu item in the IDE to email a report that includes a full description of the bug, steps to reproduce the bug, images of the bug, any component that displays the bug, and the database needed to reproduce the bug.

          If we can't reproduce a bug, we can't really fix it.

          Comment


            #20
            Re: Release Candidate for Next Update

            Originally posted by Atta View Post
            Downloaded the beta and installed. When I open a grid that is made with an earlier version it takes a lot longer to open the Live Preview, and the search box now disappears of the right side of the screen

            This is a good example of a 'bug' report that is of very little value to us because:

            1. there is no attachment that allows us to reproduce the problem
            2. there are no instructions that allow us to set up a test case of our own.

            There is most definitely no generic problem with the search box disappearing.

            The live Preview speed has not changed. Depending on what version you have previously loaded, Live Preview was not properly publishing custom css and images, which is now does. So the first Live Preview might appear to be slower.

            Comment


              #21
              Re: Release Candidate for Next Update

              Originally posted by Karaiskakis View Post
              i have install the beta patches on both my Development machine and my VPS - Application Server. I think that most of the problems are solved. No fatal errors are coming out now with using grid linkers etc...
              However on my local machine when I test the application, PDF reports are shown normally.. But after publishing to VPS I do get errors - unable to print PDF reports.
              I uninstalled once again application server form VPS - reinstall it again and then used the beta patch but nothing happened.
              Something more to do on this PDF report print error??

              This is the actual error report:
              Report did not print. Error reported was:


              Layout name: Report4@[PathAlias.ADB_Path]\doctorsall2009.ddd
              Layout type: report
              OLE Automation Error. Source is CDINTF~2." DriverInit failed"

              What to do next?

              Regards
              Marios Karaiskakis

              I can't duplicate this. The error message seems to indicate that the Alpha Five Printer is no longer installed, or not properly installed.

              You might try:
              1. rebooting the machine.
              2. delete the 'alphafivev4' printer from the printers control panel.
              3. reinstall the app server from scratch
              4. reapply the patch.

              Comment


                #22
                Re: Release Candidate for Next Update

                Thank you so much!!
                This seems to solve the problem.
                First I did restart my machine but the problem continued...
                then I did as you said delete the Alpha5 printer then reinstall aplication server (without unistalling) and then i installed the patch. I think that now everything is back to normal again! Need to do more tests.

                Thank you for your help,
                Regards,
                Marios Karaiskakis

                Comment


                  #23
                  Re: Release Candidate for Next Update

                  Selwyn,

                  See this thread - I can confirm the problem that Chad has reported. Works in LP not when published.

                  http://msgboard.alphasoftware.com/al...329#post527329
                  Bill Griffin
                  Parkell, Inc

                  Comment


                    #24
                    Re: Release Candidate for Next Update

                    Originally posted by Bill Griffin View Post
                    Selwyn,

                    See this thread - I can confirm the problem that Chad has reported. Works in LP not when published.

                    http://msgboard.alphasoftware.com/al...329#post527329
                    I take that back, I resolved the problem, see the threas above for my explanation...
                    Bill Griffin
                    Parkell, Inc

                    Comment


                      #25
                      Re: Release Candidate for Next Update

                      I think this one is ready.
                      Cheers
                      Mauricio

                      Comment


                        #26
                        Re: Release Candidate for Next Update

                        No issues so far other than my ongoing Tabbed UI issues everything else seems good.
                        Chad Brown

                        Comment


                          #27
                          Re: Release Candidate for Next Update

                          Selwyn sent me off some new patch files which fixed all of my issues with the tabbed UI

                          session variable for headers now works
                          session variables now work for filters or arguments fixed
                          mystery changes on path for button i.e reports fixed

                          Had one glitch on a ajax callback in a comboedit but removed the lookup saved it and then put it back on saved and published and it was back up and running

                          Thanks
                          Chad Brown

                          Comment


                            #28
                            Re: Release Candidate for Next Update

                            Chad can we have this patch Selwyn sent you?
                            Cheers
                            Mauricio

                            Comment


                              #29
                              Re: Release Candidate for Next Update

                              I found that there is a problem with PDF report printing while working inside a frame.
                              The rest of the application runs without any problem only the pdf report issue (403 forbidden error is coming) ONLY when working in a FRAME - is this a bug?
                              should we run web applications in frames or not...

                              Marios

                              Comment


                                #30
                                Re: Release Candidate for Next Update

                                I will ask Selywn and get back to you asap.
                                Chad Brown

                                Comment

                                Working...
                                X