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

Memo Database

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

    Memo Database

    Hello all!

    When I worked in a government computer environment (about 100 years ago) we had, in the computer room, an on-line file we called "OPSTAT". It was a large memo type file in which all the information and routines were placed by the operators on an ongoing basis. So, for example, if I made a change to the system configuration or installed something new or whatever, I logged it into the Opstat log file. At the end of each month the file was archived and a new one was begun. Now this was done using DEC and DCL (Dec command language), but the upthrust was that anyone authorized could view the file and be brought up to date with what was going on in the computer systems area. In fact, we made it required reading for all operators coming on shift, so they couldn't say that they were not aware of some problem or other. It was also searchable, so that if I were looking for a particular user name or system, etc. it would locate the "hit's" for me.

    OK. My question is developmental. How can I do this in A5? I'm concerned that the memo fields are not robust enough to withstand constant opening and closing and I'm not sure how they can be searched anyway. Has anyone else encountered this problem and/or does anyone have an idea of how to address this problem? Should I use a Word file, or a searchable PDF file perhaps? I was thinking of logging the note into a memo field and then writing that memo field to a Word file.

    Thanks for any ideas you might have.

    Charlie

    #2
    Re: Memo Database

    Hi Charles,

    I'm not sure memo fields are an issue - provided that users are prohibited form navigating when they are open in any way. If you put the memo in a modal form so edits are isolated from navigation and users are forced to save or cancel any edits, you'll probably be safe from memo corruption. Lots of backups can't hurt either.

    I believe memo fields are searchable, but I don't use dbf any more unless for an old client.

    I don't know your needs, of course, but I would consider searchable category fields rather than stuff a whole bunch on info in a single memo field. But maybe that's not a good solution for you?
    Peter
    AlphaBase Solutions, LLC

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


    Comment


      #3
      Re: Memo Database

      Oh, you're in web ( I thought it was desktop). Memo fields should be safe, but I guess it depends on how Alpha handles read/writes in web-dbf.

      But if your in web, you should seriously consider a SQl backend.
      Peter
      AlphaBase Solutions, LLC

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


      Comment


        #4
        Re: Memo Database

        Memo fields can be auto saved when navigating away from the field. That's how I handled the problem.
        Another way is a set with small succint 250k fields spawned off the header. Then you can capture the viewer as well by insisting that the field was opened full size to create an activity.
        See our Hybrid Option here;
        https://hybridapps.example-software.com/


        Apologies to anyone I haven't managed to upset yet.
        You are held in a queue and I will get to you soon.

        Comment

        Working...
        X