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

MySQL back-end with Alpha Five front-end?

  • Filter
  • Time
  • Show
Clear All
new posts

  • MySQL back-end with Alpha Five front-end?

    I am new to Alpha Five. I purchased it for various reason (reporting, etc..), But, now I need to create an inventory application and my first inclination is to go with a SQL back-end like MySQL (it that really possible, or do I have to use the native .dbf format?)

    I would have multiple users 10 -20 in at the same time. Doing Inventory check-in, picking, shipping etc...

    I realize these details are fairly light. But just trying to get a feel for the fit for this purpose. I am going to be evaluating small WHMS, but I have a preference for creating the app to fit our needs not vice-versa.


  • #2
    Re: MySQL back-end with Alpha Five front-end?

    Hey everyone! We got ourselves another convert!


    Alpha, of course, works well with other back ends. I don't know that you have a specific reason or reasons to use something other than the .dbf. And without hearing more from you, my first take is that the .dbf will handle your needs just fine.

    There's a discussion at the top of the Database Design part of this message board that's of related interest. And, of course, the links at the bottom of this thread.


    • #3
      Re: MySQL back-end with Alpha Five front-end?

      Steve Workings knows more than I do about this.

      pretty much, If you are only going to have that many users and all local, you will be better off with native tables. If you plan on making a web app later, you might think about sql, but I believe it unecessary. I have close to 20 running now and one forum regular has in the hundreds on a lan.

      Others will chime in if i am wrong, but I believ you can use the native dbf files on your own server even with sql(not sure about the sql part). i am working on that now and hope to complete a web side app soon similar to the app i have and a lot more.

      welcome to the community.
      Dave Mason
      Skype is dave.mason46


      • #4
        Re: MySQL back-end with Alpha Five front-end?

        Thanks everyone. I will be digging into this in the next month.



        • #5
          Re: MySQL back-end with Alpha Five front-end?

          Originally posted by groycvg View Post
          I am new to Alpha Five. I purchased it for various reason (reporting, etc..), But, now I need to create an inventory application and my first inclination is to go with a SQL back-end like MySQL (it that really possible, or do I have to use the native .dbf format?)
          In my (limited) experience, the dbf files - and to some degree also the desktop apps written in A5 - are very useful for data that is used as a lookup for things that don't change that often (or are only changed by a few users compared to the main portion of the data).

          Another thing I have found them easier to use for than SQL databases is for storing data that is used to customise an application further (such as images for each department's or customer's controls/web area etc, assignment of departments to staff members and so forth), and for financial and other data that is accessed more locally, by fewer people, or that you want to isolate from remote access as opposed to data that is accessible to a wider audience.

          The greater manipulation afforded by desktop apps also means that for my apps, I use them mostly for administrative uses and users, whereas the more straightforward and more limited web interfaces, which run mostly on our Oracle database, are what the majority of users interact with.

          Active link tables give a lot more power to what you can do with the desktop side of things though :)