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

Image Reference Fields again

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

    Image Reference Fields again

    How do I configure Alpha to select a specific folder and image extension from the IRF Icon which appears when you click on the IRF field?

    Alternatively, where does Alpha store the folder and type value after the first drill down and selection?

    Once the image folder has been opened, subsequent changes to the same field on the same form will display the previously selected folder and file type.

    I thought that I had this covered, but going back through many backups suggests I made it up!
    See our Hybrid Option here;
    https://hybridapps.example-software.com/


    Apologies to anyone I haven't managed to upset yet.
    You are held in a queue and I will get to you soon.

    #2
    Re: Image Reference Fields again

    Hi Ted,
    There seems to be some help available in the links at the bottom - see Editing Image File Reference Fields on the use of encode and decode functions...
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

    Comment


      #3
      Re: Image Reference Fields again

      I have looked at the help Robin.
      Unfortunately I cannot make an IRF default to a specific image.
      It is a default I am after.
      See our Hybrid Option here;
      https://hybridapps.example-software.com/


      Apologies to anyone I haven't managed to upset yet.
      You are held in a queue and I will get to you soon.

      Comment


        #4
        Re: Image Reference Fields again

        In the application startup (autoexec) we define a number of image locations which are placed into global variables. In our case almost all of those locations are set as sub-folders of the main application folder, for which we have a global variable called "App_path". The image paths don't have to be in app_path, and we have some that are not, but it makes things a lot easier if they are. So for our driver's licences we use
        Code:
        dim global IRF as c = App_Path + Tex-Images" + Chr(92)
        (I always include the Chr(92) in the path variable definition). I have a standard jpg image called "NoImageAvailable.jpg" which contains those words. I place a copy of that image in each of the image sub-folders.

        I populate the image fields in almost all of our forms using xbasic code in the form OnFetch event. I no longer use IRF fields for display purposes. The OnFetch code populates form bitmap controls. I used to use the OnFetch code to try to fix the IRF image path/filename but it was wholly unreliable in a multi-user environment. Using the Bitmap controls eliminated my problems. (Big shout out to Tom Henkel who recommended this approach and saved my sanity!) The OnFetch code is always fetching an image whose name is based on some value available in the form like a customer_id and, if for some reason that image is not available, uses the "NoImageAvailable.jpg" in its place.

        In some forms I have used field rules, default value to set the value (click both boxes) for the image to be something like "Var->IRF + "NoImageAvailable.jpg". This way, an image path/file name is automatically inserted on record save when done in the UI.

        You refer to an icon that appears when the IRF is activated. I'm not sure what you are referring to there. If I have an IRF field on a form and need to change it - I use the right click event for the image field which allows the image to be changed or deleted. If the "IRF + NoImageAvailable.jpg" has been saved on record creation, right clicking and selecting "Change Image", the system automatically points to the IRF folder and shows the JPG images there. If nothing has been saved previously, the file box may point anywhere (the app folder, alpha's exe location etc).

        The only thing stored in the IRF field is the path and file name for the image. Using Image_Filename_encode should enable the image to always be found if the app location is moved, but works only if the image is stored in a location in or below the application path.

        Hope this helps
        Finian

        Comment


          #5
          Re: Image Reference Fields again

          Thanks Finian for the detailed explanation.
          It's late here, will explore tomorrow.
          See our Hybrid Option here;
          https://hybridapps.example-software.com/


          Apologies to anyone I haven't managed to upset yet.
          You are held in a queue and I will get to you soon.

          Comment

          Working...
          X