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

MySQL or shadowed databases

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

  • MySQL or shadowed databases

    About 5 years ago I wrote my first database application using A5v9 for a local company. Much to my amazement the company have successfully ran their business using this database with only the odd minor hitch (my amazement is not a slight on Alpha 5, but the fact that someone who has never done more than dabbled with relational databases can create a stable application with the software). Over the years many new features have been added, to the point where it has become a bit of a monster.

    My client has recently updated their server, which necessitated upgrading to A5v11. Although this went pretty smoothly (just a few problems with scripts no longer working - soon sorted), we are thinking that it may be time for a complete rewrite to take advantage of some of the new features (and to clean up my novice coding). I was wondering if it is worthwhile switching to MySQL rather than continuing with the A5 database.
    • As there are never more than about 6 concurrent users on the system, which runs with shadowed databases on all workstations, I am guessing that there would be no perceptible speed advantages.
    • If running MySQL on the server would the workstations work directly on this, or would they still run shadowed versions?
    • Would a switch to MySQL negate the need to check indexes?
    • Would a switch to MySQL get rid of the occasional memo field corruption (long text field being stored in the same table)?


    I welcome your thoughts.
    If computers are so clever how come someone as dumb as me has to tell them what to do?

  • #2
    Re: MySQL or shadowed databases

    Using MySql on the desktop there are 3 options:
    1. Active Link Tables
    2. Web Components on the desktop
    3. xdialog
    • The last 2 don't require active link tables which are a bit of a pain, although not terrible.
    • Xdialog is a pain IMHO - hand code everything.
    • Web Components offers a nice choice provided you have install control, which it sounds like you do. (there have been reports of web components not registering when using an install package).


    I am guessing that there would be no perceptible speed advantages.

    Active link negates any speed advantage. But you would have to do some simple tests with the others. DBF on the desktop is fast.

    If running MySQL on the server would the workstations work directly on this, or would they still run shadowed versions?

    Shadowing is a dbf feature. Not sure what the implications of shadowing an active link table is, maybe that would work? Don't know.

    Would a switch to MySQL negate the need to check indexes?

    Correct. No data worries - unless you deliberately trash certain files.

    Would a switch to MySQL get rid of the occasional memo field corruption (long text field being stored in the same table)?

    Ditto. No data corruption. No need to store "memo" fields in a secondary table. No data worries.

    Of course, going to MySQL means recoding all your scripts/functions - as may be needed.
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com


    Comment


    • #3
      Re: MySQL or shadowed databases

      Thanks for the reply Peter. I can see that much experimentation with v11 is required before making a final decision
      If computers are so clever how come someone as dumb as me has to tell them what to do?

      Comment

      Working...
      X