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

Desktop elements not used for web apps

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

    Desktop elements not used for web apps

    I'm a new user planning to build a web application. There are elements that are used for desktop apps but are not used for web apps. For example, it is my understanding that forms or browses are not used in web apps. How about sets, reports, field rules? It would be useful to have a list of elements and features are not applicable to web apps. Could someone point me to a right direction?

    #2
    Re: Desktop elements not used for web apps

    And then there are plenty of forms and browses in the Web Application Demo that comes with A5v10. What are those used for?

    Comment


      #3
      Re: Desktop elements not used for web apps

      Right, forms & browses are desktop only. The web has grids, dialogs and a5w pages. Reports, yes. If you are using dbf (as vs SQL) you can use field rules too, but not all of them work on the web side. Sets can be used for reports only. You can get "set" functionality w. grids using row expanders and the like. Remember , desktop and web are two different animals - both in terms of functionality and in concept (connected vs. "disconnected" models).
      Peter
      AlphaBase Solutions, LLC

      [email protected]
      https://www.alphabasesolutions.com


      Comment


        #4
        Re: Desktop elements not used for web apps

        Thanks Peter.

        I started my learning of A5 with the control panel and all it's functionalities. Then I started studying the web part, it became clear that most of what I've learned are not useful for web. My point is, if the desktop and web apps are different "animals" then they should be put in different "cages". Meaning, there should be 3 control panels: a general one (or database) for everything that is common for desktop and web, desktop control panel and web control panel - a clear separation between the desktop and web parts.

        Let me break down your reply and a few questions:

        1) Forms and browses are desktop only.
        2) Reports are shown as PDFs.
        3) Sets are used for reports only. Then how do you connect different tables?
        4) Which field rules are used for web (masks, validation, lookup)?
        5) How about rest of the control panel (letters, labels, operations, code)- are these used for the web?

        Comment


          #5
          Re: Desktop elements not used for web apps

          Originally posted by alartm View Post
          As you know the regular CP is for the desktop, although for web apps you use it for reports and other things. The web CP is only for the web side. A 3rd CP as you suggest seems to me to be unnecessary. As you gain familiarity and more experience w. A5, I think you will be ok w. that arrangement.
          1) Forms and browses are desktop only.
          Right

          2) Reports are shown as PDFs.
          The WAS automatically renders your reports as PDFs.

          3) Sets are used for reports only. Then how do you connect different tables?
          You can think of a grid as a browse or a form, both. You can connect grids in 1:M relationships using row expanders and other methods. Effectively they work like sets. Very powerful.

          4) Which field rules are used for web (masks, validation, lookup)?
          Autoincrement and calculated field rules have always been web friendly from day 1. Unfortunately, Alpha doesn't give us a list of which FRs work on the web side. You will have to experiment. Grids have their own "field rules", such as validation etc, that you can apply.

          5) How about rest of the control panel (letters, labels, operations, code)- are these used for the web?
          I believe you can use letters/labels (never tried myself). Operation code can be generated and cut & paste into web side, but will typically require some minor modification. Grids can contain user defined code. Ditto for a5w pages.
          Peter
          AlphaBase Solutions, LLC

          [email protected]
          https://www.alphabasesolutions.com


          Comment


            #6
            Re: Desktop elements not used for web apps

            Couple additions:

            Reports can also be output in HTML, XLS or TXT.

            Sets can also be used the web. I use them in dialog AfterValidate and code on A5W pages.

            Speaking of Sets, one of the best pieces of advice I found here is to always base your web reports on Sets. If you change your report, you just re-publish the set and don't have to worry about overwriting a database table.
            Steve Wood
            See my profile on IADN

            Comment

            Working...
            X