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

fetch a bitmap re-visited?

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

    fetch a bitmap re-visited?

    Hi:

    Having searched the archive and found again the discussions under "pointing a record to a .jpb" I have incorporated the following into the onfetch action for a form:

    "pname=parentform:bmp_name.value
    IF trim(pname)=""
    pname="nil.bmp"
    END IF
    IF right(trim(pname),4)".bmp"
    pname=trim(pname)+".bmp"
    END IF
    pname=a5.get_path()+chr(92)+"photos"+chr(92)+trim(pname)
    IF .not.file.exists(pname)
    pname=a5.get_path()+chr(92)+"photos"+chr(92)+"nil.bmp"
    END IF
    parentform:bitmap3.bitmap.filename=pname
    END"


    All is well in so much as the coding correctly loads the right bitmap file linked to a record. BUT whenever the form is initially loaded a warning message appears stating

    Warning: Cannot locate bitmap file "*.BMP"

    In the original thread it was suggested that by deleting the bitmap object from the form and then re-doing it would solve this, but not so?

    With my limited coding knowledge I would guess that when the form is loaded the bitmap object is loading before the onfetch code and therefore at that time it cannot locate a bitmap (because there is not one shown in the properties for the object) If I am right does anyone know how I can stop this from happening?

    Regards

    Glen
    Glen Schild



    My Blog


    #2
    RE: fetch a bitmap re-visited?

    Cal Locklin gave me this script, which I have used successfully. Here are a couple things to check:

    1. Make sure a copy of your NIL.BMP is located in the sub-folder and ALSO in the folder in which you have your app. If it's not in the app folder, you'll get an error.

    2. In the properties for the bitmap, it should by checked as load from file, and you should specify NIL.BMP as the file name.

    I'm pretty sure this will do the trick for you. Let me know if it doesn't.

    Comment


      #3
      RE: fetch a bitmap re-visited?

      Bill:

      Thanks for the prompt response.

      Just pointed to the nil.bmp image in the sub directory (photos) and that has resolved it, now working a dream

      Thanks again

      Glen
      Glen Schild



      My Blog

      Comment


        #4
        RE: fetch a bitmap re-visited?

        Bill,

        I'd like to see the script that Cal shared.

        Please ;)

        Tom

        Comment


          #5
          RE: fetch a bitmap re-visited?

          Tom,

          I'm pretty sure it was the same as what Glen used in the first post for this thread. (But, it was months ago so...?)

          Cal

          Comment


            #6
            RE: fetch a bitmap re-visited?

            Thomas:

            If you do a search under "pointing a record to a .jpb" you will see the script as above but including Cal's full instructions.

            As ever, thanks to Cal for yet another solution!

            Regards

            Glen
            Glen Schild



            My Blog

            Comment

            Working...
            X