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

Runtime or Development

  • Filter
  • Time
  • Show
Clear All
new posts

    Runtime or Development

    Is there a way for a script to detect whether the user opened the database with the runtime engine or with the development version?

    -- tom

    RE: Runtime or Development

    I'll take a shot at getting this thread rolling, probably presenting to you
    the obvious.
    As far as I am aware, there is no simple way of determining whether the full
    version is in use, or the runtime. VERSION() only returns the build, and the
    wrong one at that.
    My first thoughts were to try to trigger an error by running some feature
    that is disallowed in the runtime, then trapping the error. Unfortunately,
    there is no error code listed for "full version only" features.
    (I thought there was an error message, but I might have been thinking of A4, or
    A5v1). It's possible that an error code exists, but is unlisted in the
    documentation, but one would still need a way to trigger it and nothing comes to
    mind. Perhaps someone can think of something along these lines.
    My second thought was to look at the HELP, ABOUT ALPHA FIVE sub-menu, as the
    program info is listed there, but I see no way to access it's contents.
    My last thought is a workable solution, but perhaps others will suggest
    better solutions.
    Are you using "Wise" installer, or some other installation
    program? If so, this following idea is easier. If not, this might be
    tough to achieve manually. Here goes:
    Create a file, perhaps a text file. We'll call it VERSION.TXT for this
    example. Install it in the runtime version directory. Use
    :A5.GET_EXE_PATH() to determine the Alpha.exe path, then determine if the file
    VERSION.TXT exists (or doesn't exist if using the full version) using
    Here's where using an installation program would help, as it would be easier
    to implement future installations of the runtime.
    I scanned the runtime and full version files... they appear to be the same
    size, ruling out comparing files of fixed size to determine which version is in
    You could also remove the A5DBGWIN.EXE file from the runtime directory as a
    version marker, but perhaps there is a reason that it is included with the
    runtime files, as unlikely as that may be...
    It has been several hours since your post, and knowing you as we all do, you
    probably had this answered minutes after your post, but I thought it might make
    an interesting topic...


      RE: Runtime or Development

      Craig, thanks for the suggestions. I have not been able to come up with a good solution to this one.

      I'm trying to build a script which will close the database if it's opened with the development version, but leave it open if it's opened with the runtime version.

      I can find the exe folder when the database opens. If the text file is not present I can close the database. If the text file is present, the database remains open.

      Now the trick is to figure out how to assure that the text file is stored in the runtime exe folder, only. Still working on that one.

      -- tom


        RE: Runtime or Development

        I use this text file idea to check if a computer is network optimized or not so i can tell whether to update when I startup. The only thing I could think of was this text file.

        I finally struck on the idea of putting the text file in the root directory...everybody has a c: !

        The only caution is you have to pick a name that won't be needed by any other program.
        Pat Bremkamp
        MindKicks Consulting