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

Restrict Data Entry entire database

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

    Restrict Data Entry entire database

    Hi all,

    I wanted to ask the collective conscienceness here before starting a tedious process.

    I have a reason to want the Entire database to restrict changes/saves. IOW I do not want the user to be able to do any data entry or to be able to change any current records for ANY table. This restriction to be conditional via the only button that will allow a change to a logical field.

    I am wondering if the easiest way is via Field Rules for each and every table using the CanSaveRecord within the Events tab? Or is there some function/setting that could be changed to accomplish the same thing?

    Maybe a way to change the form's "Enter Record" and "Change Record" restriction settings for all forms using a logical value to toggle it (knowing that browses would have to become all "Read Only" in addition)?

    ANY ideas would be welcome...especially those that save me time!

    Always looking for the easy way out I am!! :D
    Mike
    __________________________________________
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau
    __________________________________________




    #2
    Re: Restrict Data Entry entire database

    We have a similar situation in that we don't really want everyone changing customer information. What I do is to set a Global variable logical flag when the user signs on, and test it in the on_init of a form. If it is ".F.", then I restrict the form with an "this.allow_change=.F.". I think it is better than just restricting the entire database as you will need to do maintenance and changes, which, in a restricted database, could be difficult. One other method woud be to have a "User" version of the database that is an exact copy of your production database, but it is restricted. The only drawback here is to make sure things are always in synch.

    Just some thoughts...

    Tom

    Comment


      #3
      Re: Restrict Data Entry entire database

      Hi Tom,

      Thanks for answering.

      Maybe a bit more information on my part is in order to understand the need of entire database restriction (aside from one button).

      I am mimicing a feature in my current software I use for my business. A oft used feature my software calls a "Snapshot" is what I am reproducing---all it is really is a way to Archive files in zip files and then be able to recall the data of any Archive to look at and crete reports against. The current data would then be restored via the "Current_Data" file made prior to opening up an older Archive file (and then deleting the "Current_Data" file). It has workied flawlessly with my current software but I added a failsafe for the data just in case something corrupted the "Current_Data" file by also backing up the data right before opening up the Archive file.

      This is done basically by creating a temporary Archive file called "Current_Data" and then overwriting the databases data with the older Archive file. When the older Archive file is being viewed is when I do not want any changes or entries made.

      After reading what I just wrote I am thinking that perhaps it is the Archive files themselves that should have the restrictions placed--may be easiest solution but would have to modify my Restore from Archive script is all.
      Then it would be great if there was a way to simply restrict the entire database--very little coding to do then with the aforementioned process.


      edit--BTW-I have the entire process working for this feature except for this step.
      Last edited by MikeC; 09-24-2007, 10:05 AM. Reason: more info
      Mike
      __________________________________________
      It is only when we forget all our learning that we begin to know.
      It's not what you look at that matters, it's what you see.
      Henry David Thoreau
      __________________________________________



      Comment


        #4
        Re: Restrict Data Entry entire database

        Had a bit of time today while working to think more on this (kinda nice having a job like that, eh?!!).

        I am now of a mind to use a global variable much like Tom uses but using it with the CanSaveRecord and CanDeleteRecord events for each table--I guess it will be easy enough to do once a script is created and then simply cut and paste it into the 40 or so table's field rule events. The global variable I am thinking should go in my autoexec, the Open Archive, and Restore Current Data scripts.

        Another reason I guess for doing it this way is so I can easily give a message whenever a user tries to enter or change a value when viewing an Archive.

        Unless someone else has a better idea or can see some sort of pitfall with doing this, this is the route I will take.

        Thanks to anyone who has looked at these ramblings!
        Mike
        __________________________________________
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau
        __________________________________________



        Comment

        Working...
        X