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

Distributing an application

  • Filter
  • Time
  • Show
Clear All
new posts

    Distributing an application

    I am trying to establish a solid foolproof distribution routine and would like to share input from others so that I can make improvements.

    So the application is now ready and we need to prepare it for distribution while the built in Alpha install is very good, I think that I am correct in saying that there is no option to write to the Windows registry so for this reason alone I always use Astrum Installer.

    These are the steps that I presently take but would like input from others so that I can establish a solid distribution routine:

    1. I always add a discreet button within the application so that if at any time the locations get moved or deleted or another program hijacks the .dlls we can always tell the user by phone how to re-register the .dlls that V9 requires without having to complete a re-install required and this is the script that I use:

    prompt=ui_msg_box("Note","This action will re-register important DLL controls, continue?",36)
    If prompt<>6 then
    end if


    pfile.write_line("regsvr32.exe "+chr(34)+rtime_folder+chr(92)+"a5controls.dll"+chr(34))
    pfile.write_line("regsvr32.exe "+chr(34)+rtime_folder+chr(92)+"A5ContextEval.dll"+chr(34))
    pfile.write_line("regsvr32.exe "+chr(34)+rtime_folder+chr(92)+"SimpleChart4Lite.dll"+chr(34))
    pfile.write_line("regsvr32.exe "+chr(34)+rtime_folder+chr(92)+"Codejock.PropertyGrid.v11.1.3.ocx"+chr(34))
    if file_exists(filename) then
    ui_msg_box("Note","File not found")
    End If

    2. Add ‘license.key’ text file into the dbase folder (I also write it to the registry but I'm not certain of the ideal procedure or the outcome)
    3. Compact the dbase and then assign table password then encrypt the tables.
    4. Compile the scripts and functions to the default path then export the scripts and functions to a custom location.
    5. Delete ALL scripts and functions
    6. I now create the install using a pre-saved Astrum file taking care to register the above .dlls by using the ‘Advanced’ option and placing the App and Runtime in separate folders within the default folder. I no longer create a startup file or shortcut since reading Cal Locklin’s thread on how to create the shortcuts from within Astrum.

    (I personally always now name the engine as V9Runtime so that the ‘V’ will always be below my apps alphabetically in the tree, I have proved that some versions of Vista will not print or preview reports without a load of error message appearing if the engine is situated above the App. I know some people will disagree but I have proved this and can force/unforce the error messages by moving the location of the engine)

    I have these questions that I hope others can make clear:

    1. Does any one know of a method to remove ALL scripts and functions other than right clicking and deleting one by one?

    2. Alpha states that if loading on to Vista OS, the Vista UAC control must be turned to ‘Off’, I would like to hear of other Runtime distributor’s experiences.
    3. When using Option ENCRYPTED_TOKENS function to protect ALL scripts, is this OK to have in only one of the compiled scripts or does it need to be in each compiled script?


    Re: Distributing an application

    Cal's post #18 (right after yours in the thread linked) states a few answers to your questions....and Cal says he has a utility that will delete all scripts, etc.

    EDIT: I see that you have seen that and have also posted back to same.....
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau