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

DBF vs SQL - pros and cons ...

  • Filter
  • Time
  • Show
Clear All
new posts

  • DBF vs SQL - pros and cons ...

    I am wondering if people can chime in with what are the considerations for using DBF vs SQL.

    It seems to em that one obvoious advantage to DBF is that it is native to a5, and is what we are familar with. However, I am very concerned about index issues that have been mentioaned elsewhere. I am wondering if MySQL would completely alleviate the index problem?

    If so, how difficult would it be to migrate an entire application to SQL?

    And certainly there are other considerations that many users would hopefully be interested in hearing about - at least I am interested!

    Gary S. Traub, Ph.D.

  • #2
    Re: DBF vs SQL - pros and cons ...

    Hi Gary,
    Bet the reason you're not getting anyone's attention is that this has been discussed a few times and there is one thread that is very recent..check the Similar Threads located at the bottom of this one and you'll find a couple.
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau


    • #3
      Re: DBF vs SQL - pros and cons ...

      Hi Gary,

      The first question one needs to ask is... Do I need SQL ? Will my application become so complex overtime that SQL would definitely benefit from it ? Do you have other 'products' that rely on SQL which would interact with the Alpha application ?

      Converting from DBF to SQL should be straightforware but requires work (be it a lot depending on the complexity of the application).

      At my job I use SQL all the time because it is enterprise related. I use Alpha for my hobby project. The SQL is great when there is interaction required by so many other products for Business Intelligence purposes but would I use it for a small website ? No, not a chance.

      The bottom line: it all depends what the application would be used for.




      • #4
        Re: DBF vs SQL - pros and cons ...

        Hi guys,

        Thanks for your reply. I did read the other thread, and maybe I should have posted my question there. But I was hoping to get a more thorough discussion of more of the pros and cons.

        Here are some examples of some relevant questions, most of which were not touched on in the other thread:

        1. Speed issues

        2. Difficulty in implementing SQL vs DBF, specifically with alpha - e.g. dbf has a long tested history with alpha, but what about SQL files. What issues might come up that alpha is not as well able to handle?

        3. Security issues?

        4. Speed with very large tables - e..g., let's say millions of records.

        5. Chance of corrupted indexes of SQL vs DBF

        6. What other software would be needed e.g., I run a complex WAS app with just Windows XP - would I need 2003 server or soemthing like that if the app were using SQL.

        7. What about hardware - does SQL require more powerful computer relative to DBF?

        8. Would all queries have to be rewritten or is that handled by alpha?

        And this is just for starters.

        Since alpha has been using DBF files for decades, pretty much all the issues have been worked out over time. Not so with SQL. So I was hoping to start this thread to have a place to discuss all the issues that have come up or could come up as one comtemplates beginning to migrate to SQL.

        Gary S. Traub, Ph.D.