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

UML modeling

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

    UML modeling

    Is there any point to utilizing UML when designing an Alpha app? UML is geared for OOP languages. Som UML programs will acutually produce code and objects from the model. I realize that it's not possible to do with Alpha, however it might be good practice for documentation purposes.

    #2
    RE: UML modeling

    Hi Terry,

    Whatever you refer to them as: UML, Schema Designs, Achitecture Specs, ect....

    Yes,Yes,Yes. The more detailed your pre-production efforts become. The more consistant your designs will be and the more equipped you will be to revisit the sysetem for upgrades at a later date.


    Marc
    www.a5solutions.com
    Marc King
    A5solutions

    Comment


      #3
      RE: UML modeling

      A lot of the advantages of UML are not available for A5 but it is a standard and, as Marc points out, the more detailed your design, the better results you're going to get.

      Back before the code-generation tools were any good, people still used design languages with great effect--just a lot of up front leg work.

      And it is possible (though challenging) to code A5 in an object-oriented style. Whether or not it's worth it probably would depend on how good your design doc was.

      Comment


        #4
        RE: UML modeling

        Thanks,

        That's the answer I hoped to get. I love A5, however after using Access for many years, kicking around Visual FoxPro and Delphi, is miss some of the ease of code re-use and inheritance. Access doesn't really have inheritance, but I found it easier to manage the code modules. However, A5 is by far the easiest Db to make apps with, I suppose libraries in A5 can bu used the same way as a module. I'd be interested in how others manage apps with many global UDF's.

        Thanks - Terry

        Comment


          #5
          RE: UML modeling

          That's the answer I hoped to get. I love A5, however after using Access for many years, kicking around Visual FoxPro and Delphi, is miss some of the ease of code re-use and inheritance.

          Boy, you're telling me? :-)

          Access doesn't really have inheritance, but I found it easier to manage the code modules.

          I hear ya.

          However, A5 is by far the easiest Db to make apps with,

          Delphi is broader and deeper than the other products mentioned, and its database scheme is more "detached" or "abstract", so it is, in that sense, "harder". I've found, however, that the greater the extent of the project, the less important, em, instant gratification becomes, and the more important traditional programming tools (things that increase robustness, flexibility and maintainability) become.

          I suppose libraries in A5 can bu used the same way as a module.

          I don't know Access well enough to say. I need to experiment more with A5's libraries, too. I've managed to encapsulate certain code in A5 subforms as a sort of kluge to get inheritance, too.

          I'd be interested in how others manage apps with many global UDF's.

          So far, we've been keeping our routines separate and just sort of going "OK, I changed 'routine x'". Or more likely, "Here's everything. I don't remember what I changed." It's a work-in-progress. Heh.

          Comment

          Working...
          X