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



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

bitmap property on report

  • Filter
  • Time
  • Show
Clear All
new posts

  • bitmap property on report

    I would like to be able to insert my "bitmap" during the printing process

    i put these codes in "ON PRINT INIT" event
    in hope to be able to print a different bitmap depending on which user
    start the print job, my bitmap is nothing more than a picture of a signature
    of individual user.

    I discover that, i am not able to change or force the report's bitmap
    with these code.

    appreciate your assistance...

    Ken Tjia

    dim pfile as c AS C
    dim signature_data_path as c = alltrim(lookupc("f","a","signature_data_drive","parameter","pointer"))
    pfile = alltrim(signature_data_path) + alltrim(user_data1) + ".bmp"
    filename = alltrim(pfile)
    purchase_order_cdn:Picture.bitmap.filename = filename

  • #2
    Re: bitmap property on report

    I think the first thing is to see if it is something in your syntax, missing variable, etc before anything else--do this by hardcoding in the path in the latest part of your script and then, if working, works backwards doing the same until it breaks. IOW Narrow it down.

    If it is a syntax or whathaveyou problem, your code is missing some things ("parameter", "Pointer", user_data1, etc.) which may have to be known by others in order to diagnose....along with "dim pfile as c AS C" which is the first time I have seen this and would think it is incorrect (shouldn't as c AS C just be as C ??).
    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


    • #3
      Re: bitmap property on report

      Hi Mike,
      sorry for the extra "as c", but that is not the problem for sure.
      i have been using ui_msg_box(filename,"")
      amd i do see the patch clearly


      i just check again, the bitmap never changed
      when i alter the user id = 1002

      i remain getting 1001's signature or bitmap


      • #4
        Re: bitmap property on report

        You have my guess above as to what to do. Unless others have other guesses on how to proceed, a sample database illustrating the problem with instructions would be the easiest by far (for me at least) to figure out the problem. If you happen to attach such a sample I would gladly check it out later on this afternoon (early am here now).

        edit: it may very well be something that has to be done prior to the Report's OnPrintInit event.
        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


        • #5
          Re: bitmap property on report

          yes Mike,
          thanks for the note, i have just now put a permananet bitmap
          for example.. signature_x.bmp on the report

          each time, before the report start, i copy the current user's signature over

          filecopy(filename,signature_x)? forgot the proper syntax

          it works, as long as no 2 users try to print around the same time,
          the chance of one user replacing other's users's siganture

          it works for this morning hi, will see why, i still would like to see the object's property changed

          ken tjia