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

HTML Memo does not print correctly, why?

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

    #16
    Re: HTML Memo does not print correctly, why?

    Hi Al, Jaryder,

    The example is already there..... please look at the zip.file from Tom, and the comments I gave on that, and the screenprints I provided on that. All together, they make a complete and working example of the problem.

    I am looking forward to your comments once you have studied those if you would. You will find that indeed, parts of the HTML text is simply missing in the preview, and suddenly "back" once turned back and forth a page in print preview.

    Greets,
    MRichard

    Comment


      #17
      Re: HTML Memo does not print correctly, why?

      MRichard,

      It was my understanding that the example posted was created by Tom and not your program that you are having a problem with. I Did not see any preview problems with the data provided in Tom's example even with following your instructions.

      Sorry I was not able to help or confirm a problem.

      Later. OK I looked at the first example created by Tom and after you add a second record I do see the issue.
      Last edited by jaryder; 04-13-2009, 05:56 PM.
      Jeff Ryder

      Comment


        #18
        Re: HTML Memo does not print correctly, why?

        Originally posted by MRichard View Post

        The example is already there..... please look at the zip.file from Tom, and the comments I gave on that,
        "What we have here is failure to communicate."

        I'm not interested in Tom's example of what he thinks might be the problem that you are having... (and note that Tom reluctantly supplied that example..)

        My point is that if you are going to submit an example to Selwyn, you should first submit it here before adding to Selwyn's busy list of project items to do..

        We really are trying to help you. Please help us help you....
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.
        "Make it as simple as possible, but not simpler."
        Albert Einstein

        http://www.iadn.com/images/media/iadn_member.png

        Comment


          #19
          Re: HTML Memo does not print correctly, why?

          Al,

          I don't see the point of your persistance in me offering another example of the problem, where a working example already is on the board?

          Reluctant or not, the example nicely provided by Tom is exactly showing what the problem is, as is also confirmed by Jaryder yesterday as you can read in his post.
          I do no see a point in putting 2 working examples on the board?

          Now, back to the problem, it would be nice if you could spare some time and look into that first example of Tom, and confirm that you also see the same problem?

          Comment


            #20
            Re: HTML Memo does not print correctly, why?

            I don't have v9 so this might be irrelevant, but then again, it might be applicable.
            I opened Tom's example. At first on Preview the notes didn't show at all. Fair enough. I did what I sometimes do in circumstances like this:
            Tom's Note (the HTML which shouldn't be much different than RTF) reside in an object on the report that is about an inch high or so.
            Do this:
            Expand the Details area as much as you can and do the same with the note object.
            Voila! Everything show just fine.

            Again, I don't know if it will make a difference in v9 but give it a try.

            Comment


              #21
              Re: HTML Memo does not print correctly, why?

              Hi mr Gabriel.

              I know this solution to work sometimes as a workaround towards RTF memos, however, it did not provide a solution in this example. That would be strange also, because the field is marked as able to shrink and grow on demand.

              I have filed a bug-report on this issue.

              I hope it can be resolved, because the RTF Memo field is not quite a match for the HTML Memo field in terms of features for the user, like the possibility to implement images.

              Comment


                #22
                Re: HTML Memo does not print correctly, why?

                I have filed a completely documented bug-report on this issue with zipped files, a detailed duplication manual of the issue etc on april 14th.

                Until now I did not receive any reaction, nor confirmation of good receipt, nor a bug-fix was published.

                Is this typical for Alpha Five at the moment?

                Comment


                  #23
                  Re: HTML Memo does not print correctly, why?

                  Heres a Dumb Question Did you resize your report to hold that many lines of text in the report. I changed sizing in the report and was able to get 1st record then made a 2nd record cut paste and was able to see it all.
                  https://www.housingeducator.org
                  k3srg

                  Comment


                    #24
                    Re: HTML Memo does not print correctly, why?

                    Hi Steve!

                    I am not quite sure what you mean by 'resizing the report' ?
                    The field on the report is actually set to be able to shrink and both grow, so that imho should be enough to make any size of text fit onto the report?
                    Which setting exactly do you refer to?

                    Regards,
                    MRichard

                    Comment


                      #25
                      Re: HTML Memo does not print correctly, why?

                      Unfortunately, scince 23-04 no reaction whatever from Alpha Software on the filed documented bug report. No confirmation of receipt or anything.
                      Several weeks have gone by, and I am still in the dark about whether I can use this feature in my database solution or not. As is, I can not.
                      But the software is already programmed completely using it.
                      So, the question now is should or can I wait until this bug is fixed, or should I remove the HTML Memo Field from the database abandon it and replace it with a Rixch Text Memo, losing the ability to have the customer implement pictures in the text where he wants them.
                      I am disappointed that there is no reaction to a filed bug report.
                      The customer brings in work to report the bug, and there seems to be no understanding of even sending a confirmation that it is under research or whatever, which could even be done automatically. I can not understand that.

                      Comment


                        #26
                        Re: HTML Memo does not print correctly, why?

                        MRichard,
                        A few last thoughts for you from someone who has just read through this entire thread.

                        No response from Alpha can mean various things but, more often than not, it is due to not being able to reproduce the "bug".

                        Verification of a "bug" is usually done (for reasons stated earlier in this thread and also in hundreds of other threads) prior to submitting as one. Your comment of
                        I don't see the point of your persistance in me offering another example of the problem, where a working example already is on the board?
                        is something that goes way beyond my scope of discernment as to why or how someone would think in this way. IOW I ,for one, would not be able to explain this point to you.

                        Would a sample from you now help....maybe, maybe not. I am thinking most involved here have simply moved on.

                        That said, I am in agreement that regardless of reasons, Alpha could have a better way of acknowledgement of bug reports.
                        Mike
                        __________________________________________
                        It is only when we forget all our learning that we begin to know.
                        It's not what you look at that matters, it's what you see.
                        Henry David Thoreau
                        __________________________________________



                        Comment


                          #27
                          Re: HTML Memo does not print correctly, why?

                          This will be my very last post regarding this subject.

                          I am very disappointed in this product and the way bug reports are dealt with.

                          I emailed a complete bug report to the specified e-mail address with detailed information about a month ago, and got no reply, answer or confirmation whatever. Apparantly, it does not concern Alpha very much if their users are struggling with problems or not. I find that very dissatisfactory.

                          I have read often, that Support officers of Alpha intervene on this forum when users are struggling with problems. I understand that is not an obligation in any way, and this is at first a users platform. But especially in cases where bugs are concerned that totally block the use of sold functionality, I would expect at least some attention and communication of the vendor of the software, if not on this forum then as an answer to the bug-report I sended them. Unfortunately, neither one has been the case. I am simply left hanging out to dry, and I find that not acceptable.

                          From reading this forums posts, I found that a lot of freeware solutions are incorporated in the Alpha Five products. It might be possible that those solutions in itself contain bugs, and therefore can not easily be fixed by Alpha itself. The question comes to mind whether the use of freeware is such a great choice when your endproduct gets affected by it in this way.
                          But this is only a guess, because, as I explained, I have gotten no reaction from them until today.

                          However, for me it is time to move on to a better product, that actually DOES work.

                          My solution needs to have HTML memo capability, and if that function simply does not operate as it should in the Alpha product (which I think I and others have proven sufficiently) it is time to push it aside and look further for better products. I have given this over a month, and nothing happened in between with regards to bug or solution, and I simply can not fix bugs myself, and I can not think of a proper workaround either.

                          Very disappointing. Goodbye Alpha.
                          May you and your bug-report handling improve in time.

                          Comment


                            #28
                            Re: HTML Memo does not print correctly, why?

                            Sorry to here of your disappointment MRichard. You have had some very capable people look at this unfortunately you have not got Alpha's attention on what is definitely a bug.

                            As I use HTML memo fields, but as yet have had no reason for printing them out, I thought I had better have a look for future reference so I did some playing around with Stan's example 1 and found exactly what you have been seeing at first. The overall size of the HTML field for record 1 was correct but not all the text was being parsed to it. Take out all the blank lines in the memo and run the report again and hey-presto it's all there. This is not how it should be and Alpha need to do something about this, otherwise others may be stumped by this problem and like you leave. I will submit this as a bug as well.

                            Comment


                              #29
                              Re: HTML Memo does not print correctly, why?

                              Thank you Lance.

                              I would be gratefull if indeed you would also report this as a bug. Until now it seemed that there were no other users needing this feature. And that won't get it any easier on the bug repair list, but another bug-report possibly will.

                              I will give it some more time and see what happens. Please keep me posted about the results/reactions you hopefully get on this thread if you will?

                              Thanks,

                              MRichard

                              Comment


                                #30
                                Re: HTML Memo does not print correctly, why?

                                IMO, A bug is a bug... whether one person runs into it today... or a hundred tomorrow. Alpha should have at least acknowledged it. I wouldn't be surprised, however, to find it's been fixed for the next release.

                                Comment

                                Working...
                                X