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

Runtime install question to what am I missing here in hiding details?

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

    Runtime install question to what am I missing here in hiding details?

    HI,
    I built a desktop application and packaged it up. Now if I send it to a potential client as a demo to install on the clients machine it installs the run-time, but as that run-time installs it has all the information as to how the application was developed, where to go for more information, phone, etc.

    Now after install there is an Alpha shortcut along with my application shortcut.

    Am I missing the boat here and doing something wrong?
    I tried the .exe file from runtime install on my development machine, but I got missing file messages and it did not start.

    Now if this is normal and I am doing this right then the client could say I can have my IT guy maybe build applications like this and maybe I can use parts of demo to jump start application? Even if it can't be used, it sends message that easy development is available and that's what Alpha is all about.

    Now other than the compiled code to AEX, the tables and forms all seem to be there and as a client I could go buy Alpha Anywhere and use tables and forms, I am guessing unless you encrypt them maybe.
    I haven't looked to see what you can do with application install and the name of the tables, sets, etc.

    I'm new here, so is the potential client installing demo supposed to see the run-time install information?
    Can that be hidden?
    Do I need to drop back versions to achieve this as I am just doing desktop application at this time?

    I hide everything on application so it says nothing about Alpha Software and does not show loading screen, but the run-time installing says it all. Why bother hiding the details in your application if this is the case?

    If you click and look at file details of the run-time it has a digital signature and Alpha details there too even though you change its name.

    If I am going to spend time learning code, then maybe there's another way that is better in a rapid application development package.

    I guess that is the pitfall with Alpha if this has to be displayed to the end user.

    I was told when I bought the run-time that you can hide everything so the end user does not know how you built the application and at this moment I don't see that is true.

    Thank you for any comments to this is it and that is the case.
    Last edited by datacaster; 06-21-2018, 01:56 PM.

    #2
    Re: Runtime install question to what am I missing here in hiding details?

    Password protect everything.
    Hide the Control Panel
    Hide the Windows bar
    Then, no one can easily edit your stuff, even when using the app startup bypass routine and their own copy but they can see it and use it.
    Also, suggest you put in a robust EULA addressing IPR for the app which need to be clicked before it will run.
    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


      #3
      Re: Runtime install question to what am I missing here in hiding details?

      Thank you Ted for your words of wisdom.

      Paul

      Comment


        #4
        Re: Runtime install question to what am I missing here in hiding details?

        find the command line options for starting alpha like -nosplash and -title =""


        They are in the help files.
        Dave Mason
        [email protected]
        Skype is dave.mason46

        Comment


          #5
          Re: Runtime install question to what am I missing here in hiding details?

          Originally posted by datacaster View Post
          I was told when I bought the run-time that you can hide everything so the end user does not know how you built the application and at this moment I don't see that is true.

          Thank you for any comments to this is it and that is the case.

          Because you have to use Alphas own runtime installer this is for sure not the case. User will see that you are actually installing Alpha Anywhere runtime product. Also every time you use Alphas runtime installer( and you have no other option) it checks your license for AA runtime. So if any errors client will see them (AA runtime error messages).

          So you are actually installing a solution for AA runtime not an own application I would say.

          edit: when I did say AA runtime will check license I mean it will check it from Alphas license server
          Last edited by kkfin; 06-25-2018, 02:14 PM.

          Comment


            #6
            Re: Runtime install question to what am I missing here in hiding details?

            You do not HAVE to use alpha's runtime installer, although it is much easier. I use astrum installer to package an alredy deployed runtime on drive C:\ locally. Then use astrum to register all the needed files and install the couple .ese's in the runtime similar to what they do with Wise installer. Clients never see the alpha name that way.

            I also create a startup exe to run alpha, so the end user does not ever need to use alpha5.exe for anything. All they would normally have to do is look at the startup link to see where and what.
            Dave Mason
            [email protected]
            Skype is dave.mason46

            Comment

            Working...
            X