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

Avoiding memo fields

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

    Avoiding memo fields

    Hi,
    I am making an app in A5, which will use data from Alpha 4 v6. I realise that I will lose the data in the memo fields now in A4 when transfering files to A5.
    The client list table in A4 has a memo field, but most of the records do not use it - it is only for remarks on some records.
    From this forum it seems best to avoid memo fields in A5. Is it a good plan to have a character table linked to the client list table, so that I can have remarks available for some records without ocupying the space in all the client list records?

    Brian

    #2
    RE: Avoiding memo fields

    Brian

    Don't worry about space, just put the comments field directly in the same table. Linking to another table is only suggested with memo fields and that is only because a corrupted memo won't effect the rest of the table. If you are using a character field for comments, linking would only add complication.

    In any case, I would suggest not converting the A4 table directly. Build a new table and append the data. This is a good way to make cirrecting in the structure and also verify all of the data when it converts.

    Jerry

    Comment


      #3
      RE: Avoiding memo fields

      Brian,

      Since disk space is very cheap I'd put the character type field in the primary table structure. It will be easier to maintain and use. -- tom

      Comment


        #4
        RE: Avoiding memo fields

        Hi,
        Thanks for the advice, I�ll just do that and put in an extra field.
        Brian

        Comment


          #5
          RE: Avoiding memo fields

          Hi,
          Thanks for the advice, I�ll just do that and put in an extra field.
          Brian

          Comment


            #6
            RE: Avoiding memo fields

            That'd be okay if you could put CR LFs in the field which as far as I can see you can't. A MEMO field on the other hand allows this.

            Comment


              #7
              RE: Avoiding memo fields

              I transfered data from A4V6 ALSO and have every bit of the MEMO field data. I see no problem with using the MEMO fields what so ever. There was a discussion about not saving the MEMO. That is if you ONLY save the MEMO. IF you SAVE the record with save on the form ALSO it is saved. Was for me every time I tried it.

              Ken

              Comment


                #8
                RE: Avoiding memo fields

                Hi,

                The memo file from A4 is in a *.dbt format, whereas a memo file in A5 is in a *.fpt format. If you open your database files (or preferably a copy of your files) in A5 and then restructure the table containing the memo field, the format will be converted from *.dbt to *.fpt. The memo will no longer be readable in A4 as a *.fpt file. If you want to append files used in A4 to files used in A5, and they contain memo fields, it would probably be best to open the A4 files (or preferably a copy) and restructure the memo file to *.fpt, AND THEN append the files to the A5 files (otherwise, you're mixing apples and oranges and are probably headed for some memo corruption problems).

                Best regards,
                Robin Sculthorpe

                Comment

                Working...
                X