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

Why would certain columns not be available?

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

    Why would certain columns not be available?

    I'm accessing my tables and views from my SQL database. It's been working great. I just ran into a view that has probably 20 columns, but only about 8 of them are appearing within Alpha 5....

    I have refreshed within Alpha 5, even tho there is nothing new with the view....

    Any ideas why some columns aren't available?
    MSQL since 2010
    A5V11 since Feb 2012

    #2
    Re: Why would certain columns not be available?

    This is just a wild guess. Are the columns in your select statement?
    Or could the data be way long and their is some kind of a space restriction?
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com


    Comment


      #3
      Re: Why would certain columns not be available?

      Hi Peter -

      Thanks for the wild guess -
      I 'solved' it for the moment by:
      Create view vViewNamenew as Select * from vViewNameSource

      and, from Alpha5, I can access all the columns from vViewNameNew (even though I cannot from vViewNameSource)

      so, for the time being, I'm up and running.

      As I'm just learning, playing and evaluating, the work-around is fine. I was mostly trying to find out if there were some Big Picture Rules that I was not aware of.


      The column that I wanted in particular was nothing special at all - just an integer - that I wanted to access as PK!!!!
      MSQL since 2010
      A5V11 since Feb 2012

      Comment


        #4
        Re: Why would certain columns not be available?

        You are probably using .dbf type tables.

        I found that a Grid with two .dbf tables "joined" on common columns containing a "code" would display data in columns from the secondary table but only blanks from the primary table in Grid rows where the matching code was missing (or had been deleted) from the primary table.

        Comment


          #5
          Re: Why would certain columns not be available?

          Originally posted by DB_Dan View Post
          You are probably using .dbf type tables.
          Originally posted by MarionT View Post
          I'm accessing my tables and views from my SQL database.
          Peter
          AlphaBase Solutions, LLC

          [email protected]
          https://www.alphabasesolutions.com


          Comment


            #6
            Re: Why would certain columns not be available?

            I know this is an old thread, but I am running into this problem.

            I am using the Edit Sql in Query Builder to write the statement -
            Select * from Entity
            WHERE EntityID in (Select EntityID from vContract)

            I get the following error:
            Could not get information about table 'Entity', Error reported was Error 2099 - Not Found
            Error looking for column 'EntityCityCode' while processing contraint in in TableInfoGetContraints.

            When I click out of that error I get:
            Script: UI_DLG_BOX:wcb_window02052012141851queryCSline:1109
            tempIndx = tempPPK.arrTables.find(ut(pk.arrTables[tempI].name),"ut(name)")
            Property not found
            pk.arrTables[] subelement not found


            I can't imagine what is wrong - my Entity table is fine and healthy.... in SQL

            But in Alpha 5 it is wonky. I get the right data in a grid, but if I try to do anything with it via the SQL builder, I get totally wrong columns, error messages, etc.

            What would cause Alpha5 and a SQL table to not play nicely togehter?
            MSQL since 2010
            A5V11 since Feb 2012

            Comment


              #7
              Re: Why would certain columns not be available? - > Progress, but still problematic

              OK - Since the error message talked about constraint issues, I went to SQL. It was confusing, because, within Design Mode, I right clicked and saw that I didn't have any Constraints set.

              However, when I told my SQL mentor about my problem, he said explained that SQL Designer was only checking for CHECK CONSTRAINTS. But, since I had set DEFAULT CONSTRAINTS, Alpha 5 was seeing those.

              I've removed the constraints. Now, when I access the table thru the SQL Genie, it does, indeed, see columns.

              Unfortunately, those columns are not part of this table......

              They were, once upon a time, but not now.

              I will find an alternative way to do what I need, without the Genie.
              MSQL since 2010
              A5V11 since Feb 2012

              Comment


                #8
                Re: Why would certain columns not be available?

                UPdate on this.

                The problem is related to SCHEMA names.

                I have the following tables in my SQL DB:
                dbo.Entity
                Venue.Entity

                Depending on where I am in Alpha5, Alpha5 insists that the columns from Venue.Entity are in both tables.

                I renamed my Venue.Entity table.

                Now, Alpha 5 recognizes the two tables as 2 distinct, separate tables.

                It seems that A5 is not fully qualifying their queries with schema.name in every place under the hood.....
                MSQL since 2010
                A5V11 since Feb 2012

                Comment

                Working...
                X