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

A5v9 Heirarchy... Does it exist?

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

    A5v9 Heirarchy... Does it exist?

    I am part of a small I.S. shop (3 of us) and we decided to move our Alpha Database environment to MY local C: drive until a replacement server comes in. No problem, right? NOT.

    I 'shutdown' my workstation about twice a week (no particular reason other than to reset things) after I run a DEFRAG and then boot. The problem is, if another user logs into the databases ahead of me (after my workstation is up and running) I cannot access the databases. Which means, I have to chase down my cohort to have him get out of the way.

    The issue created seems to be related to how the Alpha looks at which user has logged in first. Why does this matter? And how can I fix it? When we had the databases on the server (before it broke) this wasn't an issue. What's the difference?

    FYI: No one other than I.S., uses the databases. But we do plan to make a Help Desk Ticket database environment for the entire company that will be used by a couple hundred users after things are put in place. Of course, at that time, we won't have the databases on my C: drive. They will be on their own server.

    #2
    Re: A5v9 Heirarchy... Does it exist?

    The problem is, if another user logs into the databases ahead of me (after my workstation is up and running) I cannot access the databases.
    This is not a normal situation but I'm not completely clear on what you are saying. You have substituted your machine for the server effectively? The other user(s) are accessing the database across the network to your machine?

    What does "I cannot access the databases" mean? Do you get an error?
    There can be only one.

    Comment


      #3
      Re: A5v9 Heirarchy... Does it exist?

      "Yes" to both of your questions about replacing the server with my C: drive AND the users going across the network to get to my C: drive. As for me not being able to access the databases; it's just that. I cannot open them at all. I can log into Alpha5 but not any of the databases. (That is, until the other user logs out and let's me go in ahead of him.)

      I'll get you the error message after our startup tomorrow morning.

      Until then, do you have any ideas as to what the cause is? Has this come up. I can't find a post that addresses it.

      Comment


        #4
        Re: A5v9 Heirarchy... Does it exist?

        First thought here is that your license from Alpha is being maxed out by the other users, so your access to the database is blocked until one of them shuts down.

        Comment


          #5
          Re: A5v9 Heirarchy... Does it exist?

          (That is, until the other user logs out and let's me go in ahead of him.)
          Tom's idea sounds right but this is puzzling.

          If you log in first then he can log in as well? But if he logs in first, you can't?
          There can be only one.

          Comment


            #6
            Re: A5v9 Heirarchy... Does it exist?

            The licensing isn't a problem. We have two developer's licenses and there are only 2 of us doing the development work. (The 3rd I.S. guy is our manager and he doesn't touch things.)

            Right, Stan... As long as I log in first things work just fine. No error messages or anything like that.

            That is why I was wondering if there was some kind of heirarchy in Alpha5. Or maybe it has something to do with it being placed on my C: drive instead of a typical server. I can't imagine why that would matter but, I guess anything is possible.

            Comment


              #7
              Re: A5v9 Heirarchy... Does it exist?

              Since your machine is not a server, what operating system? What system for your cohort?

              Here's an article about using xp file sharing that might help.
              There can be only one.

              Comment


                #8
                Re: A5v9 Heirarchy... Does it exist?

                We are an XP Pro (SP3) shop on all our workstations. The I.S. workstations are no different. The thing is, I used the same workstation (mine) as the beta environment when we first got A5v9, last year. The only difference is that it is now shared. Otherwise, everything is as it was.

                Comment


                  #9
                  Re: A5v9 Heirarchy... Does it exist?

                  It happened again this morning. My cohort-in-crime logged in first and I could not get in until he moved out of the way. What makes this strange is, if I get in first we can BOTH use/see/edit the databases. But if he gets in first only HE can move around. I can't do anything. What's that about?!

                  Comment


                    #10
                    Re: A5v9 Heirarchy... Does it exist?

                    And the error message is..................
                    There can be only one.

                    Comment


                      #11
                      Re: A5v9 Heirarchy... Does it exist?

                      I didn't get a chance to get a screen shot (much less write down) the error message but... It says the user license has reached its limit and that someone needs to log off. The problem with the message is, we are both coming into work after having logged out the previous night, so the logins are fresh. And we have A5v9 (2 developers' licenses, unlimited users, etc.).

                      Comment


                        #12
                        Re: A5v9 Heirarchy... Does it exist?

                        Check the Help, About Alpha Five..

                        to insure that the licenses for both machines are different.
                        There can be only one.

                        Comment


                          #13
                          Re: A5v9 Heirarchy... Does it exist?

                          We've done that. My cohort is a network system's guy. Very savvy. He, and I, think it has something to do within Alpha5 itself. Right now, this isn't a critical issue but it may become one, once we put it back on the server and go "live".

                          Comment


                            #14
                            Re: A5v9 Heirarchy... Does it exist?

                            check the shortcuts on the computers
                            they should be opening alpha on each local computer and pointing to the data on the one computer.

                            If one computer is pointing to a shortcut on another computer you will get this error.

                            C:\Program Files\a5v9\alpha5v9.exe d:\some directory\****.adb

                            Charlie crimmel

                            Comment


                              #15
                              Re: A5v9 Heirarchy... Does it exist?

                              Check in Settings on the database that the license numbers are different on each PC.

                              You can get a situation like this when one of your PCs has 2 license numbers and the other has 1 ( the same as one of the ones on the other PC )registered.

                              Comment

                              Working...
                              X