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

What file to be given to client instead of Source Code?

  • Filter
  • Time
  • Show
Clear All
new posts

    Re: What file to be given to client instead of Source Code?

    Originally posted by Suvarchala View Post
    My question was, I have developed an web application on my desktop which is running on my local host.
    What files do I need to the client, so that he can able to dump in his desktop and run on his local host.

    Other than .AEX, wt else can be given?
    Alone .AEX files are fine to support database tables too.?

    Please provide information on that.

    Thanks & Regards,
    1. you want to deploy your webapps as a runtime client to his machine only running localhost.
    2. your client needs the A5V11 developer version to run the webapps on his local machine the A5 runtime is only for desktop<Windows>
    3. the internet outside world can't connect to the local apps, and if it can be done it is time limited and not for production
    4. if you don't want your client to make any changes to the code then the A5V11 "Webstarter pack for 3 concurrent users" is the best option, see the webshop for details
    5. you already received the rest of the answers howto publish your webapps for your customer



      Re: What file to be given to client instead of Source Code?

      Hi Eric,

      Thanks for your valuable information.
      I will check this Webstarter pack for 3 concurrent users.

      Thanks & Regards,


        Re: What file to be given to client instead of Source Code?


        If you have a WAS license, you don't need a starter pack. One WAS license is good for one machine (server). To host a web site you could use your own machine (if that is appropriate in your case?) -OR- you need a VPS or other dedicated server. If you don't want to give your client the source files, you can just publish them to local host and copy those files to the client server's web root. But if you copy to local host, you will need to fix the a5_application.a5i file located there because that has aliases and connection strings that will be different for the server than for localhost. You may possibly need to publish at least one object to your client's server to get that right if you can't figure out a way to do it manually.

        Also, check this out, it should give you some valuable insights:
        AlphaBase Solutions, LLC

        [email protected]


          Re: What file to be given to client instead of Source Code?


          I am not sure if your initial question was answered. You asked what files were required on the Client-side.
          The answer is of course NONE. It is a web app and your clients only need their web browser on a machine that is connected via TCP/IP to the server.
          If this was not what you were asking, then sorry for stating this very basic fact.