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

Multi User and SQL

  • Filter
  • Time
  • Show
Clear All
new posts

  • Multi User and SQL

    How much of a speed improvement can be had by using SQL as a back end in a multi-user environment? I am sure it depends on the application, but just in general.

  • #2
    Re: Multi User and SQL

    "In general," I don't think there is a meaningful (general) answer. It would depend on a whole lot of things. For example, using "active link" tables could be slower, again depending on the app. And how many users (at the same time) are we talking about? What are the users typically doing? How large are the tables? In many cases, dbf tables still make more sense, and in many cases typical operations are very fast, or plenty fast enough. It all depends on so many things.

    Raymond Lyons


    • #3
      Re: Multi User and SQL

      If you "move" the logic behind some elaboration to the database server (with stored procedures) you can have some speed improvement, because there's no need for the data of the tables to be sent to the client for the elaboration, but only the resulting set of the procedure. The cons: if you change your backend db server you must rewrite all the procedures...

      *** 38911 basic bytes free ***


      • #4
        Re: Multi User and SQL

        Another one... generally speaking, if you create a view (on db backend), the database generate also the best access path to read the tables. If you execute a query by code (running a 'SELECT x FROM y'), the access path will be rebuilt every time you execute it. With many tables involved (joined) and recurrent queries, the difference can be significant.

        Remember also that sometimes it is better to create a function on the db to perform some management than elaborate by code the same records. If you use (with attention) the db triggers you can save a lot of time avoiding the repeating of the same code in all the forms that performs some insert or update operation...

        In general: more logic in the db means more performances but the portability across db backend will suffer (for example you can write triggers on some db that works at record level, but in others only at "set" level - the entire set involved in the sql statement executed - and the code will be necessarly different between the two), more logic on the application means less performances but more db portability.

        If you know in advance that you will never change the db server, you can think to optimize the performance in that way (if in the future you change the frontend the work involved will be less).

        Hope it helps.

        *** 38911 basic bytes free ***


        • #5
          Re: Multi User and SQL

          I would suggest to use SQL databases for critical operations due to several reasons:

          1) Querys are usually processed on the server not in the client, the client only gets the results. This gives you a speed gain. However only Alpha Five Server gets the data in/out directly from SQL database, the desktop edition uses .dbf tables like temp tables for SQL database.

          2) You get rid of indexes problems, SQL are usually mission critical and most SQL versions recover automatically from shut downs.

          3) It is possible to implement transactions which ensure the operations are completed all or nothing but never on stay on the middle.

          4) Backup may be created online without having to stop database

          5) There are some more handy features like the ability to go back to a certain time, etc.



          • #6
            Re: Multi User and SQL

            I have adopted Alpha Front end and MySQL backend for the following reasons:
            a. interaction between different applications (sharing data) is simplified.
            b. licensing of apps shared by various users remotely located (geographically) is simplified
            c. you have access to more than one reporting application

            there are other reasons but the above, to me, are important.
            INFOMAS (Information Systems)