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

database design bugs

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

    database design bugs

    Greetings, i have reported this bug before and the instruction given seem to work for a bit now it don't i will list my 2 issues i hope you can help.


    1: When designing a new database and creating my forms i often switch back and fourth from structure to rules and form design. When i go back to structure i get table in use error, i try to run the a5 close all command in the interactive window, but only works sometimes, only way to clear it is to restart alpha.

    2: I noticed if i create a new table as i enter a few fields and try to save I'm getting error that row is not complete, i have tabbed through all the fields to make sure all are complete and have both added a dummy field and our deleted my last field entered to see if that clears error.

    thank you

    #2
    Re: database design bugs

    R, when you open a form in design mode or for viewing you also open the tables supporting that form. The tables are in use. If you need to make structural changes to the table you need exclusive access to the table. Make sense? So, close your form layouts first. Ok?

    Comment


      #3
      Re: database design bugs

      I make sure i close all but what I'm working on, example I'm making my form and decide i need another field, i save and close the form designer then go to structure design to add field, save and close that then reopen my form designer, I'm religious about this practice. it seems a5 isn't letting go of the closed areas. and note i have this problem on 2 totally different and non-connected systems

      Comment


        #4
        Re: database design bugs

        I noticed if i create a new table as i enter a few fields and try to save I'm getting error that row is not complete, i have tabbed through all the fields to make sure all are complete and have both added a dummy field and our deleted my last field entered to see if that clears error.
        just select rows past the end of your entries and then save it. This has been an issue for many versions in alpha. It is not bad once you figure it out.


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

        Comment


          #5
          Re: database design bugs

          Thanks DaveM i will test later today

          Comment


            #6
            Re: database design bugs

            R., I haven't experienced what you describe. Saving the changes to the layout is necessary, but until you close the layout the tables remain open. I wonder if clicking the Refresh button on the control panel toolbar, after closing the form layout, will make a difference?

            Comment


              #7
              Re: database design bugs

              Tom Cone Jr, i have tried that as well as closing current database and opening another, even in the newly opened database and i try to edit structure i get same error, i don't know of this add light to subject, but this system also running a5-v6 not at same time but its the server for my company and 7 other people are pulling info from me. now i have never had this issue while working with a5-v6 and developing new database.

              Comment


                #8
                Re: database design bugs

                now i have never had this issue while working with a5-v6 and developing new database.
                I have in all versions when I am not careful. If you suddenly have this issue, I have a feeling you have changed some way of doing things as that is, so far, the only reason I have found for some users having these problems and others not.

                I am not saying you are wrong, just that for some reason certain methods will cause these problems....as Dave said, it has been around for a while. It could be something as simple as not saving both the code and the form when making alterations. It could be that you are opening a form as dialog and not closing it from memory. Maybe when tabbing it makes Alpha do something that is causing this (I rarely tab).

                It used to happen more often to me than it does now....why did I not report it as a bug? Not reproducible on demand and not that big an issue for me were my reasons.
                Mike
                __________________________________________
                It is only when we forget all our learning that we begin to know.
                It's not what you look at that matters, it's what you see.
                Henry David Thoreau
                __________________________________________



                Comment


                  #9
                  Re: database design bugs

                  Thanks MikeC, im going to move my A5 to a dedicated development machine, so its only the OS and A5-v10 running, perhaps my system and network is causing problems with the app, As i know various system configuration and users habits can bring on strange behaviors in apps.

                  Comment


                    #10
                    Re: database design bugs

                    I would recommend never developing on the server. Two good reasons are 1) it will be much slower and 2) if it is the same adb currently in use by others, you have a high risk of causing problems: when you open a form in design mode, you are also opening the underlying table - which others may also be using. Very hazardous.

                    As far as occasionally getting the message 'file in use' when you are active in development, and are in and out and in and out of forms, field rules, structures, etc., a table will sometimes be left open or reported as such. The easiest way to deal with is just close the app and reopen it.
                    Cole Custom Programming - Terrell, Texas
                    972 524 8714
                    [email protected]

                    ____________________
                    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

                    Comment

                    Working...
                    X