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

Concurrent access to multiple workspaces

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

  • Al Buchholz
    replied
    Re: Concurrent access to multiple workspaces

    To emphasis what Stan is saying...

    You would run 2 copies of Alpha - each opening a different workspace.

    I would suggest a separate shortcut on the desktop for each occurrence of the workspace and a different color scheme on the forms to clarify to the user which workspace is open..

    Leave a comment:


  • sgerber
    replied
    Re: Concurrent access to multiple workspaces

    Originally posted by Stan Mathews View Post
    Open Alpha Five, open your workspace. Minimize it.
    Repeat with other workspace. They will run independently.

    Open another database (button).
    Well that was certainly interesting! I didn't know you could have two instances of A5 running at same time. I accidently brought up a second instance previously and got a licensing warning. Apparently that only happens when you try to bring up the same workspace in both instances. (Must detect that scenario as multi-user?).

    Thanks for pointing this out Stan. It's a minimalist solution and I don't like it, but as a failsafe it certainly works.

    I'd like to move along to the next step on the path to "seamless" integration. I checked the link you posted and don't know why you pointed it out. It talks about "opening another database", that's good, but it says it will close the first one, that's bad. Am I misundertanding something?

    1. Can you help me move toward my next and possibly last step, Stan. The only other database I have at present is my test database. That will change shortly. If I place a menu in that database, what do I need to do to access that menu from my current workspace without closing it.

    2. Secondly, Stan, you didn't answer my earlier question but I can understand because I was terribly confusing. The question was whether all the various implementations of multiple workspace access require having two workspaces fully open concurrently with two control panels.

    Thanks much ... Sam

    Leave a comment:


  • Stan Mathews
    replied
    Re: Concurrent access to multiple workspaces

    Stan, how do I do this? I'd like to see how it feels to have two control panels and if I wanted, 2 menus, one for each workspace.
    Open Alpha Five, open your workspace. Minimize it.
    Repeat with other workspace. They will run independently.

    Open another database (button).

    Leave a comment:


  • sgerber
    replied
    Re: Concurrent access to multiple workspaces

    Originally posted by Stan Mathews View Post
    I have just an inkling of what you mean.

    You can have two workspaces open simultaneously. One option.
    Stan, how do I do this? I'd like to see how it feels to have two control panels and if I wanted, 2 menus, one for each workspace.

    You can have one workspace which has a menu that opens either of two other workspaces. Second option.
    This one interests me the most Stan. It "sounds like" (??) it's what I do now. Do all 3 of these options involve actually opening the other workspace? All I can relate to is A5V1 where the primary menu brings up a 2nd menu from the other directory and you just run menu options. You don't have a sense at all that there are different directories involved. Is it like that when you're concurrently accessing two workspaces in V11?

    Here's the Version 1 button code which calls up the app menu in the other directory. In this scenario there are two directories but only a single control panel. However the control panel switches to the other directory while you're executing a form in the other directory. This probably doesn't make sense to you. I'll stop there.

    Code: app_run("C:\A5\GCXWINV\GCXW.APD", "CARD=~GCXW Main Menu~"

    You can have a button on the menu for of both workspaces which opens the other. Third option.
    I can't quite picture this. Sounds like being in two rooms with the ability to see both ways when I'm only going to be in the one room.

    Stan this all sounds terrific!!! I need to see first hand how it works and what it feels like. My son would probably want the solution that's easier.

    Could you just respond to two things at this time?

    1. My earlier question about how to have two workspaces with two control panels open concurrently.

    2. If I didn't open the other workspace (or do I have to?), can I access a menu I put there from a button on the menu in my primary workspace? If so, what would the code be for that button or where can I find it in the documentation.

    Thanks again, Stan. This is very good news. I'm very sorry my response is somewhat confusing.

    --- Sam

    Leave a comment:


  • Stan Mathews
    replied
    Re: Concurrent access to multiple workspaces

    I have just an inkling of what you mean.

    You can have two workspaces open simultaneously. One option.

    You can have one workspace which has a menu that opens either of two other workspaces. Second option.

    You can have a button on the menu for of both workspaces which opens the other. Third option.

    Leave a comment:


  • sgerber
    started a topic Concurrent access to multiple workspaces

    Concurrent access to multiple workspaces

    My son's business has both a retail and a wholesale component. My A5 application migration from V1 to V11 is almost complete. I now have to deal with a nice feature that V1 provided, "Application Cards".

    When my son started his wholesale operation I copied all the A5 files to a new directory, and emptied out all the tables. All filenames remained the same. I created an application card for the new directory (in V11 I've learned that we use forms for menus instead of application cards).

    So ... on his V1 application card I put a button that says basically, go to the wholesale directory and bring up its menu. This enabled a seamless crossover to the other directory and both menus worked concurrently. He could create an invoice for a retail customer side by side with a wholesale customer's invoice. Alpha 5 kept track of which directory was involved and there never was a problem.

    I don't know V11's nuances but I do know that it's a major pain in the butt to have to close down the first workspace to do something in the second workspace and then come back again. That's a great example of the opposite of "seamless".

    Alphaholics, is there hope for my son? Do you have a trick up your sleeves?

    For those of you who managed to escape V1, this implementation was via an "app_run" capability.

    Thanks for listening. Please have a solution. --- Sam
Working...
X