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

Multi-user conversion

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

    Multi-user conversion

    Hi everyone,

    I (my client, that is) has a stand-alone A5 4.5 application which I wrote without any particular expectation of future requirement for muti-user access. With previous "line by line" programs, I have deliberately tended to open files and update records via functions which, regardless of future expectations, could, if needed, subsequently be modified for file and record sharing and locking. As these utilities are built in to Alpha, I rather ignored this.

    You've guessed it. The application may now need to be networked, with multi-user access. What should I do, if anything, to ensure the preservation of the integrity of the database, or is this handled automatically? Obviously, the client needs to upgrade his A5 licence, but anything else?

    Many thanks for any hints, tips or pointers.

    Martin.

    #2
    RE: Multi-user conversion

    You could purchase the A5V4.5 Runtime for this purpose.

    Your application and data should reside on a server. You should install the runtime on each workstation and map a drive to the server.

    As long as your data and application are in one folder, you shouldn't find too many problems. You will have to make some adjustments such as making sure that your reports are pointing to the correct printer driver.

    gm

    Comment


      #3
      RE: Multi-user conversion

      Thanks, Gedi,

      Would it be possible to run a multi-user application over a simple "peer-to-peer" network, i.e. without a server as such?

      Thanks again for any help.

      Comment


        #4
        RE: Multi-user conversion

        Martin

        That is the most common way to network the database. One computer acts as the "server" and the others use a shadowed installation and become "terminals" In most cases, a database written as a standalone will work just fine networked. The only big issues occur if the database has hardcoded paths in code. Since the path from a terminal is different, this creates problems. If all of the paths in the standalone are relative, then there is no problem.

        Jerry

        Comment


          #5
          RE: Multi-user conversion

          Martin,

          In addition to what Jerry mentions, you will want to think through your entire application, looking for places that require exclusive access to tables in the database. If you have routines that reindex the tables, or routines that backup the tables, you will have trouble with them if you can't lock them down while you do your processing.

          If your design includes any sets with referential integrity enabled you may want to re-think this, too. A pending change in the primary table of the set will lock all the other linked records in all the child tables. This really slows things down, and of course prevents others from working with the same records. See Dr. Wayne's article at www.learn alpha.com called "Simplify Your Application", for details.

          -- tom

          Comment

          Working...
          X