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

Desktop login to multiple DBs

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

    Desktop login to multiple DBs

    Anyone sharing user security files between multiple databases?

    A desktop app has 8 copies of the same database, used for different purposes. An individual user will log in to one or more of these. On disk the folder structure is
    Code:
    Data
       DB1
       DB2
        ...
    At this time we can't have A5 use the Windows login for the credentials, so the users and groups will be in a shared file for all databases. The problem is that Alpha seems to only support putting the shared security files "in or below" each database.

    If the security files are in Data folder a warning says they are not relative to the database, so only admin can log in.

    This is not my main issue, but if this does not work then the main problem is moot.

    Bill.

    #2
    Re: Desktop login to multiple DBs

    Bill, I have a user that has a logon adb, that displays 30 different facilities (the same program in 30 different folders.)

    When they select the facility, I load that that one - but I am using addin variables to pass who they are and their "security level" and managing what they can do myself. IE: I don't use Alphas security.

    I doubt this is what you are looking for, but will throw it out as an idea.
    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


      #3
      Re: Desktop login to multiple DBs

      I tried doing the same thing a while back. I only used it in testing and never in a production environment.

      Here is a link to the thread where I discussed my findings.
      http://msgboard.alphasoftware.com/al...ad.php?t=67910
      Andrew

      Comment


        #4
        Re: Desktop login to multiple DBs

        Andy,

        This looks like it will work.

        I had tried ..\ in the path, which did not work. .\..\ seems to do the trick. So the path stored in the advanced option is
        D:\Data\DB1\.\..\security.adb

        I keep security in an external database (security.adb) vs. the users database (user.adb). That way when I replace the users database files (user.al*), any mods the user has made to users and groups is not lost.

        Since I have access to their system, this approach is simpler and faster than building a generalized patch process.

        The user has a different parent folder structure than I do, so for this to work the path to security files on Advanced tab would need to automatically change when the al* files are replaced in the user directory. This works in my tests, so I'll try production tonight.

        Bill.

        P.S. the other thing that may have been a problem was trying to set up security on the users system before copying the development dictionaries (w/ security) to production. However, I am going to declare victory and not go back to determine why some things did not work!

        Comment

        Working...
        X