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



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

Table Array Variables

  • Filter
  • Time
  • Show
Clear All
new posts

  • Table Array Variables

    I'm new to Alpha 5. My old DB required me to specify a field was an array by dimensioning it as such in the table. I can not find this or the method to do this in the documentation. Wiki describes how to use xbasic to work arrays, but what do I have to do/how do I store these in a table?

  • #2
    Re: Table Array Variables

    What kind of database was this? I've never heard of such a thing being defined for a database field


    • #3
      Re: Table Array Variables

      There is no array field type in Alpha.

      You could have an entire table to hold an array and you could save the array to a file for later retrieval.

      I suppose you could also save an array to a memo field and retrieve it from that field.
      There can be only one.


      • #4
        Re: Table Array Variables

        Originally posted by NoeticCC View Post
        What kind of database was this? I've never heard of such a thing being defined for a database field
        Filemaker Pro has something similar. It has the ability to specify a field as repeating. Which is basically allowing multiple values in the one field, which could be classed as an array.

        Multiple values in a field breaks the first rule of database normalization thereby greatly impairing the relational aspect of the database.
        Tim Kiebert
        Eagle Creek Citrus
        A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.


        • #5
          Re: Table Array Variables

          Originally posted by NoeticCC View Post
          What kind of database was this? I've never heard of such a thing being defined for a database field
          I use Clarion for most of my work. When defining the fields in their "table designer," after setting the field type, for example a dBase3 table with a field defined as an integer, I then have the option of "dimensioning" that field. It becomes part of the tables definitions, and subsequently I must state/index which "hole" I'm saving the data in when I update that field.

          I see no such item in Alpha...If I wanted to store an array within the "dbf" table that I create in do I do that? Mutiple individual fields?

          How would you hold as example (not necessarily a good one) the names of the weekdays under the variable "weekday?" In my other programs, I would just define the weekday variable as a text with a single dimension of 7...then update weekday[1] as Sunday, weekday[2] as Monday, etc.

          Is there a similar concept within Alpha?


          • #6
            Re: Table Array Variables

            The traditional approach here would be to use separate records for each weekday field value. Instead of having a single record with 7 possible values, you'd have 7 records with only one value in each. This might be useful in a lookup source table, for example. While entering data into a second table the user might "lookup" the desired weekday field value from the 7 record table.


            • #7
              Re: Table Array Variables

              There is this function in Alpha but not the complimentary which gives the reverse, that I can see (day_number("sunday") -> 1). You can make your own (I dimmed global so you can see it in variables but don't have to):
              dim vLweek as C
              for i=1 to 7
              	evaluate_template("dim global vg_day"+i+" as C="+quote(word(vLweek,i,crlf())))
              dim vweek_get as C=""
              for x = 1 to 7
              ? vweek_get
              = Sunday
              Last edited by Mike Wilson; 04-17-2011, 12:23 AM.
              Mike W
              "I rebel in at least small things to express to the world that I have not completely surrendered"


              • #8
                Re: Table Array Variables

                Thanks for the comments...guess the simple answer is that Alpha does not store "arrays" in it's data base fields...

                I guess I'm trying to fit Alpha into my "old ways" of doing things rather than learning anew.

                Thanks for your help.


                • #9
                  Re: Table Array Variables

                  Originally posted by jackp_MDB View Post
                  Thanks for the comments...guess the simple answer is that Alpha does not store "arrays" in it's data base fields...

                  I guess I'm trying to fit Alpha into my "old ways" of doing things rather than learning anew.

                  Thanks for your help.
                  Perhaps we can help your "adaptation" if you will tell us how you would use such an array when entering or editing records? i.e. what user experience do you need to replicate using Alpha tools or approaches?


                  • #10
                    Re: Table Array Variables

                    What I'm working on a schedule program. The basics are a "matrix" that is labeled as "line numbers." These are 7 lines and each assigns a "priority" for the day of the week. For example, Line #1 is 7 on Monday, 1 on Tuesday, 4 on Thursday, and 5 on Friday. Line #2 is 2 on Monday, 3 on Tuesday, 5 on Wednesday, 1 on Thursday, and 4 on Friday...etc.

                    There are seven personnel, each assigned a specific line number for the week.

                    The schedule is then published showing "priorities" based on the line numbers. As an example, Monday's lines 1-7 are priority: 7,2,3,4,5,6,1. Whom ever is assigned line 1 is priority #7, line 2 is priority #2, line 3 is priority #3, etc.

                    Priorities #1-4 always show for work, and priorities 5-7 are on "standby," but do not have to report for work unless more than the normal workload is encountered.

                    I intended to have an Monday "array" to translate the line/priority assignments into personnel names. The index 1-7 would show priority 1-7. Each weekday would hold the seven name priority and I would use the index to create the printed schedule.

                    What are your ideas to do away with the indicies?


                    • #11
                      Re: Table Array Variables

                      Jack instead of "lines" could re-state your goal in terms of columns and rows? I've read your post several times and can't tell which is which. Sorry.


                      • #12
                        Re: Table Array Variables

                        I understand what your matrix should look like. What is the source to populate the matrix? Where do the 1-7 priority levels for Monday - Friday originate?
                        Mike W
                        "I rebel in at least small things to express to the world that I have not completely surrendered"