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

Is it possible to create a VIEW in Alpha5?

  • Filter
  • Time
  • Show
Clear All
new posts

  • Is it possible to create a VIEW in Alpha5?

    Similar to an ORACLE DB VIEW or a MYSQL DB VIEW can I create a similar scenario within Alpha5? That is, create a Table that automatically updates as data is entered into other tables, etc.?

    Thanks for any suggestions or ideas.


  • #2
    I believe best practice is that you want to create the view in the native DB and then add the view to Alpha to use.
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein


    • #3
      The question is a bit vague.
      Do you want to create a view using dbf tables, or do you want to execute sql code in alpha to create a view ?
      Gregg Schmidt


      • #4
        Try developing a Set.
        They are effectively views which can be updated but you can control that.
        Views are created as they are launched and are really just joined up tables based on keys.

        If you want summat more robust, try building an OLAP cube. Processed over night, it gives an easier and less time consuming query facility over several tables. Useful when bringing data together for reporting purposes.
        Ted Giles
        Example Consulting - UK

        See our site for Alpha Support, Conversion and Upgrade.


        • #5
          Thank you for the reply's.

          I'm revisiting my attempt to upsize a fairly complex Alpha DB and thought a view might serve my purpose. However, now that I analyze it more closely there is some write back that needs to happen so a view doesn't on the surface look like a solution.

          I'll take a look at a "Set" and see if that will help.



          • #6
            Don't be surprised if you find out sql gives you better control (easier queries and faster updates) than dbf tables.
            I'm aware of the pains of making the conversion from dbf to sql, but the end result usually makes the effort worthwhile.
            Knowing what I know now, I would convert the tables first (make sure the column definitions are what you want), then
            identify relationships in your set (or the relationships you want to use).
            Gregg Schmidt


            • #7
              Depends on what you are comfortable with really. I use both depending on the type of application.
              For single user desktop, DBF is more than adequate.
              For upwards of 20 users, then I tend to go the whole Web thing with SQLServer19.
              Ted Giles
              Example Consulting - UK

              See our site for Alpha Support, Conversion and Upgrade.


              • #8
                Appreciate the responses.

                My simple mind says that if the upsizing is successful and all tables are migrated then the rest of the Forms/Reports/Operations/Code should work since the new SQL tables are essentially linked to the application.

                Yet, I'm running into Index issues and reports not working issues and that doesn't seem to make any sense?


                When I open all of the tables from Alpha that are linked to SQL they show the correct data and even the sets are working, so where might the problems be??

                For instance, this report has Tables dragged onto it and nothing has changed, those tables all work individually and have data but yet the report doesn't run/complete??? It doesn't make sense..

                Attached Files


                • #9
                  Looks like you need to (re)build the "Responsibi" Index/Query
                  Gregg Schmidt


                  • #10
                    Yep, indices in Alpha are different to an index in SQL.
                    If you try creating an index you will be offered a choice.
                    If using SQL go for that construct else you may have performance issues.

                    I think I have answered this question recently on the Forum.
                    Ted Giles
                    Example Consulting - UK

                    See our site for Alpha Support, Conversion and Upgrade.


                    • #11
                      So trying to work through a report and I don't see any options for changing its connection source??


                      All of the reports are connected to "linked" tables now and simply aren't working, the computer just runs and never returns any report data. However, if I create a new report using <SQL Data Source> a report is generated nearly instantly.

                      So this tells me there is a problem with using linked data sources and should be changed to SQL Data Source. How can I modify the reports to use a SQL Data Source instead of a Linked Data source??? That should be an easy modification I would think but I don't see an option anywhere???



                      There's also no identifier as to a SQL report vs. a non-SQL report...



                      • #12
                        Originally posted by madtowng View Post
                        Looks like you need to (re)build the "Responsibi" Index/Query
                        Testing the indexes this error is common... where can I find this script?



                        • #13
                          The method I used, and it sucked, was to create a new report. In an effort to minimize errors on my part, I would copy and paste from the dbf report to the sql report,
                          test and make necessary adjustments.
                          Gregg Schmidt


                          • #14
                            Use the [CopyTo] feature to copy the required report from the DBF to the SQL table you want to use. the selected tables you want to Copy To are not designated as SQL - Active or Passive -so pick the correct one.l
                            You will not see the usual "SQL SOURCE" when you right click the report after copying it, but the data will be from the SQL table.

                            However, as Gregg says, the best way may be start over as I am unclear as to what performance issues you may have using this approach. Suggest you try it.
                            Ted Giles
                            Example Consulting - UK

                            See our site for Alpha Support, Conversion and Upgrade.