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

Open Index

  • Filter
  • Time
  • Show
Clear All
new posts

  • Open Index

    Hi all, have a interesting problem. In a Inventory DB, I have a form that based on an Order.set. When entering parts into an embedded browse, the part_no is a lookup field, so far so good, if the part doesn't exist, you can enter the new part through an "add parts" form. When I try to enter the new parts number, I get the following error msg. "not an open index, A_tbl_part_no subproperty cannot be assigned to". haven't seen this one before, what should I look for. tks jb

  • #2
    Re: Open Index

    Hi John,

    Is this a new problem in a new app or a new problem in an old app?

    Try the basics, compact database and/or rebuild indexes.
    Keith Hubert
    Alpha Guild Member
    KHDB Management Systems
    Skype = keith.hubert

    For your day-to-day Needs, you Need an Alpha Database!


    • #3
      Re: Open Index

      John, are you setting values for A_tbl_part_no in code? Could you post some of the code?

      Saying this may be redundant, but a subproperty is a property of a property.

      Fom the help file...

      "For example, the "font" property has the following sub-properties: "bold, "color, "italic", "name", "size", "strikeout", and "underline"."

      So, are you setting a sub-property of A_tbl_part_no somewhere?


      • #4
        Re: Open Index

        John, is the error happening when you try to enter the new part using the separate "add parts" form? Does that error happen if you are doing this while the first (set based) form is closed? I'm wondering whether the set based form has locked the source table you use for your parts lookup? Is that table part of your set design ? Do you have referential integrity enabled?


        • #5
          Re: Open Index

          Thank you for the replies. Keith, new db new problem, all compacted and indexed. David, will have to check some of the code in the field rules. Tom, yes it only happens on the new part form. the set is as follows.
          parent - order_Head
          child - order_items, 1 to many, no referential
          child - vendors 1 to 1, filter .not.deleted()
          parent - vendor 1 to 1
          parent - personal 1 to 1

          the flow of the forms are - po order form, lookup on the part - lookujp form, if not there, lookup form allows new parts to be entered, opens - add parts form, when you enter the new part# and press enter to add the description, that's when the error occurs. I will go back to sq one and trace the whole process. Tks for help. jb


          • #6
            Re: Open Index

            Hi Guys, good news, found my problem. had a part_no lookup within the inventory db, removed it and everything works fine, thanks for the support. jb


            • #7
              Re: Open Index

              Originally posted by John Burke View Post
              the part_no is a lookup field, so far so good, if the part doesn't exist, you can enter the new part through an "add parts" form.
              lookup field in which table?


              • #8
                Re: Open Index

                I started writing a response, got distracted for a good hour, came back and hit "submit" only to find out you figured it out already...


                • #9
                  Re: Open Index

                  Originally posted by G Gabriel View Post
                  I started writing a response, got distracted for a good hour, came back and hit "submit" only to find out you figured it out already...
                  at least you improved your skills for just an hour