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

Mounting Frustration...

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

    Mounting Frustration...

    In my neverending quest to drive myself nuts, I've again come across something that I can't figure out how to do correctly in A5. (this would be a no brainer for me in Approach, but I'm really _trying_ to make the switch). Anyway, to the matter at hand:

    I'm doing this timekeeping doodad. Supports multiple projects. So, I have a rate schedule table (we'll call it RATES). This table has fields Projnum, Craft, Type, Rate.

    Typical values would be:

    PROJ1, TECH1, ST, 10.00
    PROJ1, TECH1, OT, 15.00
    etc..

    I also have a Timesheet Header table (TS_HDR) and a Timesheet Detail table (TS_DTL). I think the header table is moot in this issue. The detail table has fields TSnum, Projnum, EmpID, Craft, Type, Qty, Gross. The tsnum and projnum fields are set from the parent record.

    Typical values would be:

    T0001, PROJ1, DOE1234, TECH1, ST, 8, ???

    Now, How do I grab the appropriate rate from the RATES table? I assume that I'll have to use a lookup function, and the fields to match will be a combination of Projnum+Craft+Type in both tables. These filter expressions hurt my brain.

    I even tried creating fields in both tables that contain the combined fields for matching (e.g. PROJ1TECH1ST), but still can't get it working.

    EEEEEEeeek!

    R.

    #2
    RE: Mounting Frustration...

    Have you tried concatenating the 2 fields into one? For intance,
    field1 and field2. In a calc field, use field1+field2. This will
    produce the values of each like so. Suppose field1 holds nuttin and
    field2 holds honey, the calc field will display nuttinhoney.

    Comment


      #3
      RE: Mounting Frustration...

      You need a clear linking key between both tables that is in the same format in both table. Probably PROJNUM is the key field in both tables. Then add you source fields and fill fields. Are you doing this in the field rules of the header table?
      Alex Levy
      Tampa, FL

      Comment


        #4
        RE: Mounting Frustration...

        The set is structured like this:

        TSHeader - TSDetail (via TSNum)

        TSDetail - Rates (via concatenated Proj+Craft+Type)

        Concatenations are set up as field rules for the tables.

        Calcs for the Gross pay are set up as field rules for the set.

        I set up a simplified dummy app and have been able to get this to work by simply joining the tables in the set via the concatenated fields. Something must be up in my main app.

        Is it ok in a5 to link two tables more than once in the same set (via different key fields, of course)?

        Comment


          #5
          RE: Mounting Frustration...

          Hi Roy,

          Use a lookup field for the rates in the detail table.


          Something like

          Lookupn("F","RATE","Concatenated field","Rates","index name")

          "F" means the First value that matches your concatenated field.
          Rate is the amount you want to fill in. (the lookup value)
          Concatenated Field is your concatenated field.
          Rates is the DBF file to look the answer up in.
          index name is the name of an index you should create based on the concatenated field.

          I typed this out quickly but I believe that is the correct structure. It should work. If not it's close, just needs a little tweaking.

          Hope this helps,

          Dan
          Dan

          Dan Blank builds Databases
          Skype: danblank

          Comment


            #6
            RE: Mounting Frustration...

            Thanks Guys... I finally figure that one out thru trial and error. I'm not quite used to the terminology used in the manuals, but I'm rewriting in my own lingo as I learn.

            Either way, filter expressions are a pain.

            Comment

            Working...
            X