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

End of Development to Runtime

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

    End of Development to Runtime

    after 6 years using Alpha Dos i have, over the last 6 months ,updated our system to A5v5 and it works perfectly. the development was done on our w200 server with xp on our pc's. i am now ready to create our first runtime using Astrum InstallWizard and issue it to a client who has a w200 server with 5 pc xp workstations.

    there has been so much written in the forum about problems associated with runtime on installations and updating that i am very nervous in taking the next move hence my visit to the forum to get advice on the following:

    1. installation of clients runtime

    Do i install the runtime on all the 5 pc workstations and the server and then map them? or run a shadow db on the server?

    2. Alphasoftware update patches.

    How do i get these updates onto to the clients runtime versions?

    3. System Updates

    How do i get any upgrades to our master application
    ( which has no data) onto the clients system? how will this affect the data they have inputted into their system.

    i have tried to find a simple comprehensive user document that can guide me through this phase but without success.

    i very much appreciated any asistance from the forum members.

    thanks

    alan

    #2
    RE: End of Development to Runtime

    Alan

    I'll answer questions 1 and 2 and hope someone with a bit more experiance answers question 3.

    1. installation of clients runtime

    Do i install the runtime on all the 5 pc workstations and the server and then map them? or run a shadow db on the server?

    You only have to load the runtime on the 5 workstations unless you are going to use the server as a workstation also. Place your application on the server then map all the workstations to that machine. Once you have done that then from each workstation run network optimisation which will create a shadow on the workstation. Each workstation will then access the shadow database each time they use the application. If you make any changes to the application on the server then each workstation will run the refresh shadow.

    2. Alphasoftware update patches.

    How do i get these updates onto to the clients runtime versions?

    If your asking about including the latest patch at the time you install the runtime then include it on your CD and run the patch after you have installed the runtime. For future patches you will have to have each PC connected to the internet or download the patch to a CD and then distribute.


    Hope this helps.

    Rick T

    Comment


      #3
      RE: End of Development to Runtime

      Thanks Rick,

      2 down 1 to go.

      Alan

      Comment


        #4
        RE: End of Development to Runtime

        Alan

        Question 3 has been discussed frequently on the forum. There is also an article in the July 2002 newsletter about file structures that is helpful. Basically, all of your designs, scripts, function, toolbars, menus, etc are saved in data dictionary files.

        For the database itself, these are the files with the name of the database and the alb, alm, and alx file extensions. For tables, these are the files with the name of the table and the ddd, ddm, ddx file extensions. Sets are contain no data, so they are only data dictionaries and are the set, sem, sex files.

        No real data exists in the data dictionaries, just structure information. If make any changes, you can copy these files to the user database directory and they will show all of the changes. If the user is networked, copy these files to the server and then have each terminal refresh the shadow. Data only exists in the dbf, cdx, and fpt files. If you don't overwrite those, you will lose no data.

        The only exceptions to this occur if you change a table structure by adding a field or, in some cases, changing a field name. Both of these issues have a number of threads on the forum. You can search for "update" or something like that and see what you can find.

        Jerry

        Comment


          #5
          RE: End of Development to Runtime

          Thanks Jerry,

          understood and will do further research as you suggest.

          alan

          Comment


            #6
            RE: End of Development to Runtime

            As a point of conversation, I'd give some serious thought about NOT installing any patches. While a patch usually includes a bug fix, if the app is 'running perfectly', why take a chance that the future bug fixes might affect the 'perfect app'?. Sometimes it's best to leave 'well enough' alone.

            kenn
            TYVM :) kenn

            Knowing what you can achieve will not become reality until you imagine and explore.

            Comment

            Working...
            X