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

Single user to network

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

  • Single user to network

    I need your help. I have developed several information systems and now I need that the users of these information systems can share their data. I going to acquire a 10 users runtime pack.

    My question is if I do not have to modify the systems already finalized so that it can share the data.

    Thank

    Omar.

  • #2
    RE: Single user to network

    Omar,

    I'm not certain I fully understand your question. Perhaps some general information will help.

    The runtime engine will drive your application (database) just like the development version. For example, if you leave the control panel open so that you can get to it quickly when a form closes, this will also happen when the runtime user closes the form. Most of us do not want our end users to ever see the control panel, so we arrange to hide it. (After first being careful to construct a trap door we can use to show it again... often password protected).

    Since we build our apps to deny the control panel to our end users, we must build utilities or functions that this denies them also. Many of us use custom menus to give the end user the option to reindex or pack their tables. Backup and restore functionality is also often deployed, without using the control panel.

    In general the runtime will behave exactly like the development version while your app is running. If this is not what you want then you have to program around it.

    Let us know if you have more specific questions, and give us all the details we would need to understand you.

    -- tom

    Comment


    • #3
      RE: Single user to network

      No, in general you do not need "modify the systems already finalized so that it can share the data."

      However, if your systems were not designed for use by more than one user at a time, you could run into problems.

      Ray

      Comment


      • #4
        RE: Single user to network

        I appreciate very much your answers.

        Raymond, you are right, my systems were not designed for use by more than one user at a time, how can I do that.

        Comment


        • #5
          RE: Single user to network

          >>my systems were not designed for use by more than one user at a time, how can I do that.

          Comment


          • #6
            RE: Single user to network

            Hello Omar,

            >>my systems were not designed for use by more than one user at a time, how can I do that.

            Comment


            • #7
              RE: Single user to network

              Hi Jim, Hi Ray.

              Thanks by your answers. I going to follow your advice.

              Omar.

              Comment


              • #8
                RE: Single user to network

                Hi Jim

                That is a very useful list of things to consider. Could you please elaborate a little more on how actually to do the following items, or tips on what to do to best achieve them:

                10)control the app so open sessions are kept to a minimum,
                11)don't allow users to keep sessions open in enter mode while they 'go to lunch' etc.
                14)control the user tightly in the application so 'unexpected' things do not happen,
                15)do alot of error checking so you can control the environment when unexpected things happen

                Gary
                Gary S. Traub, Ph.D.

                Comment


                • #9
                  RE: Single user to network

                  Hello Gary,

                  >>10)control the app so open sessions are kept to a minimum, >11)don't allow users to keep sessions open in enter mode while they 'go to lunch' etc. >14)control the user tightly in the application so 'unexpected' things do not happen, >15)do a lot of error checking so you can control the environment when unexpected things happen

                  Comment


                  • #10
                    RE: Single user to network

                    Hi Jim,

                    Thanks for your thoughtful reply. I am essentially doing most of what you have said, but feel I need a bit more experience with what type of situations to error trap, and I have not really done much re exclusive access concepts with the exception that I do warn users before a procedure to have other users log off, but I would like it to be a bit more elegant. Thanks for your help, and you have a Happy Thanksgiving too!

                    Gary
                    Gary S. Traub, Ph.D.

                    Comment

                    Working...
                    X