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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Standalone Toolbar

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • MoGrace2U
    replied
    RE: Standalone Toolbar

    I added an if is_object("Goto Toolbar")... to the OnInit event of my Main Menu form which I am not entirely sure actually tests for a toolbar or not, but it seems to be keeping a 2nd instance of the toolbar from appearing when the databases are switched. I dumped the CanExit/ Cancel() from the MainMenu which caused optimization problems. I guess I will just have to train my users better.
    -Robin

    Leave a comment:

  • MoGrace2U
    replied
    RE: Standalone Toolbar

    Hi Tom,
    Yes I did mean databases. Sometimes they need to quickly pop up a different database but then they do not close that copy of A5. They are using the desktop shortcuts now to do this. I thought if they would use their one open copy of A5 to switch databases that would resolve the problems, but I can't get it to work right with my standalone toolbar.
    -Robin

    Leave a comment:

  • Tom Cone Jr
    replied
    RE: Standalone Toolbar

    It's been a while since I checked this, but I believe each open instance of Alpha Five counts towards the license limit.

    In my earlier suggestion I was assuming you needed to switch databases, not tables. There's a world of difference between the two.

    -- tom

    Leave a comment:

  • MoGrace2U
    replied
    RE: Standalone Toolbar

    Hi Tom,
    Right now the 3 users have 3 database files they each use. I am not sure how that effects the multiuser license count when they open 2nd and 3rd instances of A5 - which is what they are doing now. Should I even worry about this? I thought that maybe if they could switch files then record locking problems could be avoided from leaving a set open.
    I'm discovering that training adults is more of a headache than I expected!
    Thanks, Robin

    Leave a comment:

  • Tom Cone Jr
    replied
    RE: Standalone Toolbar

    Robin,

    I'd probably require the user to close the current session, shutting Alpha Five down. Then use a second shortcut to begin a new session with the other database. -- tom

    Leave a comment:

  • MoGrace2U
    started a topic Standalone Toolbar

    Standalone Toolbar

    My MainMenu form (which stays open) opens my Goto Toolbar in its OnInit event and it stays open throughout the session - so far so good. I have added a cancel() to this form's CanExit event so the user has to use my buttons to exit the program. I need to be able to switch between database files and am using the system Open Database/ Close Database. Which at the moment will not work because of the CanExit script. So I added a button to close the Main Menu form first so then the Open Database will work; however the standalone Toolbar will not close and when another database - using the same toolbar is opened, I get 2 copies of it. I set Tbar as a global variable (pointer) when opening the Goto Toolbar but Tbar.close() will not close it. I've tried testing if is_object("Goto Toolbar") but I get nothing in the interactive window when the toolbar is loaded. Toolbar launcher will close the toolbar but the 2nd instance of MainMenu OnInit will not reopen it. What am I doing wrong? I tried assigning the toolbar to the Main Menu properties but when the form is minimized the toolbar becomes hidden - therefore it needs to be a standalone. And please don't tell me that v5 will solve my problem - that is not the answer at this point in time! I've searched the board for a work around as to how I can bypass the system menu and CanExit was the only option I have found. I have Logon and Logoff scripts to run and need to be able to control the program or database file exits. Anybody - any ideas?

    Tags: None
Previous template Next
Working...
X