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

Deploy a database to end users

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

    Deploy a database to end users

    Hi, This topic may have been talked about before but i couldn't really get what i need. and i am a newbie to alpha five by the way.

    I developed an alpha five database and want to send it to end users to use. not sure how. i know i can use the install maker to make a package with application file and runtime file. however, once installed the setup.exe, all tables are pointed to the setup folder ( i.e c drive). how can all users share this database if the database tables are all in c drive?

    please forgive me if i sound dumb.

    Thanks in advance.

    #2
    Re: Deploy a database to end users

    Bradley,

    All of this has been discussed many times before all over this forum.

    1. There is a reason alpha dropped the install maker in v12.

    2. Get an installer. a good one

    3. make sure you don't put hard paths in your application. That way the app only looks at tables and so forth attached to your adb. make sure all files(except runtime) are in one folder.

    4. use shadowed tables if there are several people using the app.

    5. get a good installer

    Just trying to cover the main points here.

    Comment


      #3
      Re: Deploy a database to end users

      Multi User
      If you are installing a multi user application, the installation involves multiple steps – installing the application files on
      a shared server, installing the Runtime files on each user’s machine and (optionally) installing a “bootstrap”
      application on each user’s machine (if your application uses Network Optimization).
      IMPORTANT You should install the Alpha Five Runtime on each user’s local machine. DO NOT INSTALL A SINGLE
      COPY OF THE RUNTIME ON A SERVER FOR USERS TO SHARE FROM THEIR DESKTOPS. Doing so could result in
      serious performance degradation.
      IMPORTANT Each user must have read/write access to the folder on the server where the application files are
      installed.
      For multi user applications, you should consider taking advantage of Alpha Five’s Network Optimization feature.
      Applications that run on a network will run much more quickly if you use Network Optimization.
      Using Network Optimization
      If you want your application to use Network Optimization (recommended), then follow these steps:
      1. Install the application files on a shared folder on the server.
      2. Install the Runtime files on each user’s machine.
      3. Install a special “bootstrap” application on each user’s machine.
      For more information on creating a “bootstrap” application, see “Creating a Bootstrap Application” in the Appendix.
      Your install program for the “bootstrap” application should include a shortcut that launches the Alpha Five Runtime
      and loads the “bootstrap” application. The first time the user clicks the shortcut, the “bootstrap” application will be
      launched. This application will then prompt the user for the path to the master copy of the application (which is
      installed on the shared server) and it will then create a “shadow” copy of the application.
      The next time the user clicks the shortcut to start the application, the real application is loaded (and not the
      “bootstrap” application).
      Alpha Five Runtime 7
      Not using Network Optimization
      If you do not want to use Network Optimization (not recommended), then follow these steps:
      1. Install the application files on a shared folder on the server.
      2. Install the Runtime files on each user’s machine.
      To start the Application, a user will start the Alpha Five Runtime on ttheir machine and then use the File/Open
      command to open the application on the server.
      After the user opens the application for the first time, they can create a shortcut that will start the Runtime and also
      open the master copy of the application.
      How to Make a Shortcut
      Start Alpha Five and from the Control Panel, select the Tools, Create Shortcut… command.

      Creating a Bootstrap Application
      When you install a multi user application that uses Network Optimization, you need to install a master copy of the
      application on a shared server, and you need to have a “shadow” copy of the application on each user’s machine.
      This “shadow” application points to the master copy of the application.
      Your install program cannot install the “shadow” application on the user’s machine because (at the time you create
      the install program) you don’t have any way of knowing what the path is from the user’s machine to the server
      (because you don’t know where the user will install the master copy of the application). To get around this problem,
      you install a special “bootstrap” application on the user’s machine. The first time the user starts your application, the
      “bootstrap” application is loaded and it asks the user for the path to the master application (which is on the shared
      server). The “bootstrap” application then automatically creates the “shadow” application on the user’s machine.
      Here is how to create a "Bootstrap" application.
      1. Create a dummy application with no tables, forms etc. The name of the dummy application must be the
      same as the "Master" application. E.g. "AutoPartsStore.adb"
      2. Add an Autoexec script to the application (See below).
      Here is the code for the Autoexec Script in the “bootstrap” application:
      dim master_db_name as C
      dim shadow_db_name as C
      master_db_name = ""
      shadow_db_name = ""
      ui_modeless_dlg_box("Install MyAppName",<<%dlg%
      {can_exit=exit}
      {lf};
      Specify the filename of the master copy of the application:;
      [%P=ui_get_file("Select file","(*.adb)",master_db_name)%.100master_db_name];
      {lf};
      <Click Here to Start Install!oK?.not.(master_db_name="")> <Cancel!cancel>;
      %dlg%,<<%code%
      if a_dlg_button = "cancel" then
      ui_modeless_dlg_close("Install MyAppName")
      a_dlg_button = ""
      end if
      if a_dlg_button = "oK" then
      if file.exists(master_db_name) = .f. then
      ui_msg_box("Error","Master Database not found.")
      else
      shadow_db_name = a5.Get_Name()
      a5.Load(master_db_name)
      If version() = 5 then
      a5_NOpt_CopyAddFiles(shadow_db_name,master_db_name)
      create_shadow(shadow_db_name,master_db_name,.t.)
      Else
      create_shadow2(shadow_db_name,master_db_name,.t.)
      End If
      ui_modeless_dlg_close("Install MyAppName")
      end if
      end if
      %code%)
      Your installation program will install the "Master" copy of the application in a shared folder on the server and it will
      install the "Bootstrap" application on each runtime user's workstation.
      When the user starts the "Bootstrap" application (which in this example is called "AutoParts.adb") it will immediately
      display a dialog asking for the path to where the Master copy of "Autoparts.adb" is installed. Once the user fills this
      in and clicks the OK button, the script will automatically open the master copy of the database. It will then do the
      initial Network Optimize, and then open the shadow copy of the application on the user's machine.
      The next time that the user opens "AutoParts.adb" on his machine he automatically is working with a Network
      Optimized (i.e. “shadow”) version of the master database.
      There can be only one.

      Comment


        #4
        Re: Deploy a database to end users

        might look here for discussions. There are many many more.
        https://forum.alphasoftware.com/show...ghlight=astrum

        Comment


          #5
          Re: Deploy a database to end users

          Thanks amorris, I will have a look.


          Originally posted by amorris View Post
          Bradley,

          All of this has been discussed many times before all over this forum.

          1. There is a reason alpha dropped the install maker in v12.

          2. Get an installer. a good one

          3. make sure you don't put hard paths in your application. That way the app only looks at tables and so forth attached to your adb. make sure all files(except runtime) are in one folder.

          4. use shadowed tables if there are several people using the app.

          5. get a good installer

          Just trying to cover the main points here.

          Comment


            #6
            Re: Deploy a database to end users

            Thanks Stan, I will have a good read and try.

            Comment

            Working...
            X