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

Brain dead report table setup runtime

  • Filter
  • Time
  • Show
Clear All
new posts

  • Brain dead report table setup runtime

    Hi all,

    Here is the delimna.

    User is in runtime. They need to put their own words in letters they send out in a multi letter print as a birthday card would be a little different from one user to the next.

    needs to edit words in a report ONLY for his own use. Needs to be kept on his own workstation versus a server. OR?

    report may go to any number of clients (as a letter) so it is not just for a one time report to one client.

    There any number of letters(reports) with different wording. Right now, it is 7 reports(letters).

    Note: I am and have been using text files to hold these words on the workstations. Text formatting does not come over to the reports.

    The above is just a train of thought. There may be other ways that I am brain locked on and just can't see.

    each user has a unique id

    each record has a unique id

    each letter(report) may or may not be over 255 characters(most will be over)

    Any ideas would be helpful.

    edit: these are run from a set only that includes user and id for record.

    Last edited by DaveM; 08-31-2008, 04:31 PM.
    Dave Mason
    [email protected]
    Skype is dave.mason46

  • #2
    Re: Brain dead report table setup runtime

    Not sure if I got this right, but just off the top of my head...

    Letters 1:M Clients

    Letters table includes a memo field for the body of the letter + a user_id field.

    User logs in and a query is run showing only the user's letters.
    Each letter can gave one or more clients to mail to.
    AlphaBase Solutions, LLC

    [email protected]


    • #3
      Re: Brain dead report table setup runtime

      Would upgrading to the "run engine" make sense? They could design their own reports and letters.


      • #4
        Re: Brain dead report table setup runtime

        Peter, Tom,

        Still running this through my head.

        I am just not ready to have a user making letters and such. Maybe one day.

        Table with a rmemo field for each type of letter and a user id matching matching the user id in the names table(not the client). when that user is in the app, he can only see his own letters and also change them. a query on the form for changing letters?

        When User prints a birthday card, it only pulls the rmemo matching his and sends the letter to all selected clients with only the words in the birthday memo field?

        Am I heading right way now?

        The letters table would be on the server.

        Dave Mason
        [email protected]
        Skype is dave.mason46


        • #5
          Re: Brain dead report table setup runtime

          Originally posted by DaveM View Post
          Am I heading right way now?
          Sounds right to me.
          AlphaBase Solutions, LLC

          [email protected]


          • #6
            Re: Brain dead report table setup runtime

            Thanks Peter,

            I got it now. Just like we thought.

            Dave Mason
            [email protected]
            Skype is dave.mason46


            • #7
              Re: Brain dead report table setup runtime

              If you have difficulty linking the record that contains the memo field test to the record contianing the addressee's contact information, consider:



              • #8
                Re: Brain dead report table setup runtime


                I put it in a set with the names table as master and letters as 1-1 child. It uses the usercode id as the linking field. There can be no names record without a usercode and it is linked to the only record in letters with that same usercode.

                Now when christmas cards get sent by a user, only the users cards get printed, and ALL of his get printed. I send out around 500 a year like this. so do some others. The idea was that each user may want to send a different message.

                By the way, I am doing essentially what you did. Nice article!

                Dave Mason
                d[email protected]
                Skype is dave.mason46