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

2 A5 Databases With A Common Tbl

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

    2 A5 Databases With A Common Tbl

    Is there such a thing as having 2 A5 DataBases that access a common Table?
    What I'm trying to accomplish is:
    User A has a full-featured DataBase, many tbls, Many Menu selections, among which is ABC.tbl

    User B only needs to access ABC.tbl. , They can add delete, Print etc.

    What is the best way to do it?
    I don't want User B getting into or even "see" any other features of User A's DataBase
    First Love

    #2
    Re: 2 A5 Databases With A Common Tbl

    Yes, this is possible. I am sharing a table across 9 other databases.

    What is the best way to do it?
    Create database A and database B. Add the shared table to both databases.
    Andrew

    Comment


      #3
      Re: 2 A5 Databases With A Common Tbl

      Just remember that this is best done when both database files (.adb) are in the same directory. In that case no hard coded paths are stored in the databases, so the database could be moved to a different directory and still work fine.

      If tables from different directories are added to a database, then Alpha stores full paths and it is more difficult to move to a different location.

      Bill.

      Comment


        #4
        Re: 2 A5 Databases With A Common Tbl

        The pathing issue that Bill indicates is true. In my situation I coded a UDF that verifies the correct paths of the tables. If the database folder was moved it will drop and re-add the folder form the using the correct path.

        For your reference here is my UDF that I wrote to correct the tables.
        Code:
        'Date Created: 05-Nov-2008 09:37:25 AM
        'Last Updated: 21-Mar-2009 02:26:33 PM
        'Created By  : AWS
        'Updated By  : andy
        FUNCTION f_ins_table_loc AS L ( )
        	DIM vDB_PathC as C
        	DIM vDB_Root_PathC as C
        	DIM vDB_Path_End_FolderC as C									
        
        	vDB_PathC = a5.get_path()										'"C:\DB_Dev\test\VanCamp"
        	
        	vDB_Path_End_FolderC = lastword(a5.get_path(),chr(92))			'"VanCamp"
        	vDB_Root_PathC = stritran(vDB_PathC,vDB_Path_End_FolderC,"")	'"C:\DB_Dev\test\"
        
        	DIM vIns_PathC as C
        	DIM vIns_Root_PathC as C
        	DIM vIns_Path_End_FolderC as C
        	
        
        	vIns_PathC = table.actual_filename_get("ins")					'G:\A5Ver5\MasterIns\ins.dbf"
        '	ui_msg_box("table.actual_filename_get('ins')",vIns_PathC)
        
        '	vIns_Path_End_FolderC = lastword(stritran(vIns_PathC,"\ins.dbf",""),chr(92))	'"masterins"
        '	vIns_Root_PathC = stritran(vIns_PathC,vIns_Path_End_FolderC+"\ins.dbf","")	 	'"g:\a5ver5\"
        	
        	if upper(vIns_PathC) <> upper(vDB_Root_PathC + "Masterins\ins.dbf") .and. ("C:\\"$vDB_PathC) then
        	    ui_msg_box("","Wrong Insurance table in use" + crlf()+"Dropping " + vIns_PathC + crlf()+"Adding " + vDB_Root_PathC+"masterins\ins.dbf")	
        		file_drop_from_db(vIns_PathC)
        		file_add_to_db(vDB_Root_PathC+"\masterins\ins.dbf")
           		f_ins_table_loc = .f.						'return false if tables were wrong
           	else
        	    f_ins_table_loc = .t.		   				'return true if tables were correct
        	end if
           	
        END FUNCTION
        Andrew

        Comment


          #5
          Re: 2 A5 Databases With A Common Tbl

          A lot also depends on whether both are shadowed or not. In a medical app, run with Terminal Services, there are 30 separates folders - one for each hospital, nursing home, etc., and one for the home office. Almost all lookup tables (that are mostly static) are in the HomeOffice folder, and are used by all of the other facilities. This way when we add or change a lookup table, we don't have to propogate the changes to the other folders/adb's.

          In this case, since the path will never change and none are shadowed, pathing is not an issue.
          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


            #6
            Re: 2 A5 Databases With A Common Tbl

            Hi Tom,

            Originally posted by SMARTII View Post
            Is there such a thing as having 2 A5 DataBases that access a common Table?
            What I'm trying to accomplish is:
            User A has a full-featured DataBase, many tbls, Many Menu selections, among which is ABC.tbl

            User B only needs to access ABC.tbl. , They can add delete, Print etc.

            What is the best way to do it?
            I don't want User B getting into or even "see" any other features of User A's DataBase
            While you can share the table, it is not possible if you use Alpha's database security.

            But you could easily have features that are not active and invisible for some and present for others in the same database, simplifying common maintenance of similar or identical code and layouts.
            Regards,

            Ira J. Perlow
            Computer Systems Design


            CSDA A5 Products
            New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
            CSDA Barcode Functions

            CSDA Code Utility
            CSDA Screen Capture


            Comment


              #7
              Re: 2 A5 Databases With A Common Tbl

              I am grateful to all of you for your assistance.
              This is encouraging.
              This will be an very active table where records are added/printed/deleted daily, sometimes by 4 or more users, using different "A5 Databases", but they have just this one tbl in common.
              Fortunately, the record is a single RTF field that is populated by an I-net site, so no "changing"/"editing" will take place, just add from the site, or Print, or delete existing, that's it.
              As for Martin's idea, I do have "quasi-static" tbls used for lookups, and a common folder sounds like the ticket for 50 or so users in various locations addressing the same server.
              First Love

              Comment

              Working...
              X