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

Generic Text reports (incl. HTML)

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

  • Generic Text reports (incl. HTML)

    What I've learned about Generic Text Printers:

    In the process of creating an HTML report from A5 I learned a lot about using the Generic Text printer for reports. Here's a summary of what I learned - hope it helps make the job easier for others.

    (This isn't code but this area seemed more appropriate than the "Alpha Software General Announcements" area which sounds more like it should come from Alpha instead of users.)

    1. Set the grid for "snap to" with a size of 0.167 inches. Since a generic text sheet is 6 lines per inch, this will make each line the correct height.
    (This creates a small problem with the cursor but I feel it is offset by the reduction of mistakes caused by incorrect field sizes. The problem is that the single, flashing cursor will not show up in a field box of this size. You can still highlight one or more characters and see the highlighting or you can make the box taller while editing it.)
    2. I'm not sure it's necessary but it seemed to be helpful to double space when creating HTML reports.(See item 7. Double spacing may have been a temporary solution to that problem. I've used some single spacing recently with no problems.)
    3. Set all fonts to Courier 12. This is the size that will be printed so it will help you make sure there is enough space in the field so that all letters will be printed. (This is especially important if you are trying to create an HTML report because a missing letter in an HTML command will ruin the output completely.)
    4. Use only plain field boxes and text boxes. The field box can contain a memo field.
    5. DO NOT use RTF fields and DO NOT use field borders or underlined fonts. Also, do not use check boxes or any type of graphics - they won't print but they could cause trouble with the rest of the printout.
    6. Set all fields and text boxes to Left aligned (default) when creating HTML reports. In this case, alignment is not important to the output and it sometimes seemed to cause trouble when right alignment was used. For other reports, the use of Right or Center alignment may be a necessity.
    7. IMPORTANT: This one took me a long time to discover... I found out that the fields and text boxes must be set up so that the tab sequence moves you through them as though you were reading a book (ie, left to right and top to bottom). When the tab sequence is not correct, some lines may be printed out of sequence. (Weird but true!) Unfortunately, you cannot re-sequence them in reports as easily as you can in forms. If your tab sequence is not correct, you will have to either move them and change the text in each appropriately or cut and paste the field/text boxes for each section of the report. I've experimented with the cut and paste method and sometimes it seems to fix the problem even if you cut and paste the whole section to a new report - other times it doesn't so you'll have to experiment unless someone else can figure out the logic and post it here.

  • #2
    RE: Generic Text reports (incl. HTML)

    Oops! I forgot to click the "Use HTML" box. Let's try it again!

    What I've learned about Generic Text Printers:

    In the process of creating an HTML report from A5 I learned a lot about using the Generic Text printer for reports. Here's a summary of what I learned - hope it helps make the job easier for others.

    (This isn't code but this area seemed more appropriate than the "Alpha Software General Announcements" area which sounds more like it should come from Alpha instead of users.)

    1. Set the grid for "snap to" with a size of 0.167 inches. Since a generic text sheet is 6 lines per inch, this will make each line the correct height.
    (This creates a small problem with the cursor but I feel it is offset by the reduction of mistakes caused by incorrect field sizes. The problem is that the single, flashing cursor will not show up in a field box of this size. You can still highlight one or more characters and see the highlighting or you can make the box taller while editing it.)
    2. I'm not sure it's necessary but it seemed to be helpful to double space when creating HTML reports.(See item 7. Double spacing may have been a temporary solution to that problem. I've used some single spacing recently with no problems.)
    3. Set all fonts to Courier 12. This is the size that will be printed so it will help you make sure there is enough space in the field so that all letters will be printed. (This is especially important if you are trying to create an HTML report because a missing letter in an HTML command will ruin the output completely.)
    4. Use only plain field boxes and text boxes. The field box can contain a memo field.
    5. DO NOT use RTF fields and DO NOT use field borders or underlined fonts. Also, do not use check boxes or any type of graphics - they won't print but they could cause trouble with the rest of the printout.
    6. Set all fields and text boxes to Left aligned (default) when creating HTML reports. In this case, alignment is not important to the output and it sometimes seemed to cause trouble when right alignment was used. For other reports, the use of Right or Center alignment may be a necessity.
    7. IMPORTANT: This one took me a long time to discover... I found out that the fields and text boxes must be set up so that the tab sequence moves you through them as though you were reading a book (ie, left to right and top to bottom). When the tab sequence is not correct, some lines may be printed out of sequence. (Weird but true!) Unfortunately, you cannot re-sequence them in reports as easily as you can in forms. If your tab sequence is not correct, you will have to either move them and change the text in each appropriately or cut and paste the field/text boxes for each section of the report. I've experimented with the cut and paste method and sometimes it seems to fix the problem even if you cut and paste the whole section to a new report - other times it doesn't so you'll have to experiment unless someone else can figure out the logic and post it here.

    Comment


    • #3
      RE: Generic Text reports (incl. HTML)

      OK. The button didn't work! I'll try without it ...

      What I've learned about Generic Text Printers:

      In the process of creating an HTML report from A5 I learned a lot about using the Generic Text printer for reports. Here's a summary of what I learned - hope it helps make the job easier for others.

      (This isn't code but this area seemed more appropriate than the "Alpha Software General Announcements" area which sounds more like it should come from Alpha instead of users.)

      1. Set the grid for "snap to" with a size of 0.167 inches. Since a generic text sheet is 6 lines per inch, this will make each line the correct height.
      (This creates a small problem with the cursor but I feel it is offset by the reduction of mistakes caused by incorrect field sizes. The problem is that the single, flashing cursor will not show up in a field box of this size. You can still highlight one or more characters and see the highlighting or you can make the box taller while editing it.)
      2. I'm not sure it's necessary but it seemed to be helpful to double space when creating HTML reports.
      (See item 7. Double spacing may have been a temporary solution to that problem. I've used some single spacing recently with no problems.)
      3. Set all fonts to Courier 12. This is the size that will be printed so it will help you make sure there is enough space in the field so that all letters will be printed. (This is especially important if you are trying to create an HTML report because a missing letter in an HTML command will ruin the output completely.)
      4. Use only plain field boxes and text boxes. The field box can contain a memo field.
      5. DO NOT use RTF fields and DO NOT use field borders or underlined fonts. Also, do not use check boxes or any type of graphics - they won't print but they could cause trouble with the rest of the printout.
      6. Set all fields and text boxes to Left aligned (default) when creating HTML reports. In this case, alignment is not important to the output and it sometimes seemed to cause trouble when right alignment was used. For other reports, the use of Right or Center alignment may be a necessity.
      7. IMPORTANT: This one took me a long time to discover... I found out that the fields and text boxes must be set up so that the tab sequence moves you through them as though you were reading a book (ie, left to right and top to bottom). When the tab sequence is not correct, some lines may be printed out of sequence. (Weird but true!) Unfortunately, you cannot re-sequence them in reports as easily as you can in forms. If your tab sequence is not correct, you will have to either move them and change the text in each appropriately or cut and paste the field/text boxes for each section of the report. I've experimented with the cut and paste method and sometimes it seems to fix the problem even if you cut and paste the whole section to a new report - other times it doesn't so you'll have to experiment unless someone else can figure out the logic and post it here.

      Comment


      • #4
        RE: Generic Text reports (incl. HTML)

        Well, I never did get this to work flawlessly but it came pretty close. Here's the additional info I've discovered:

        1. The only problem seems to occur when the report is too long and additional pages are printed. The problem is that some lines of text get printed 2-3 times. Therefore, make the report form as long as possible and set the paper size to Continuous.

        2. I figured out how to get the text boxes into the correct tab order. Simply click the first box then hold the shift key and click each of the other boxes in the desired sequence. When all boxes in the group are highlighted, "cut" them from the form (CTL-X or from the menu) and re-paste them. The paste operation will put them in the correct order. (So simple but so long to figure out!)

        ANOTHER WAY:
        I have created some e-mailable HTML reports using Xbasic and the $lt;file".write_line() command. This seems to work flawlessly. For the result of one of these reports, see the attached file. Just download it and double click it. This was my second one and it took me about 4 hours to create the complete Xbasic script. It is moderately complex with 3 report groups, 2 child tables, and multiple fonts. If you are at all familiar with HTML, e-mail me for more info on how I created it. (The attached sample is just some junk text with fictitious names so don't worry about the contents, just the format.)

        Comment

        Working...
        X